Yes, my mistake, sorry, it does in fact look like it is a datetime and a datetime in MS SQL Server is compatible with an ODBC quoted ts.

However, it appears I've somewhat mislead you. The SQL Server driver I use does accept ODBC timestamp escapes in bound parameters whereas the MS one appears not to. So, if you are using the ODBC escapes with your driver you'd need to concatenate them into your SQL or pass them as plain timestamp strings in a format MS accepts.