First off, to head off suggestions that won't be particularly helpful - I know that SQL2005 is not an officially supported platform for OD6.0.2. Secondly, it's not for 6.1 either, so suggestions to upgrade probably won't be very helpful.
That said, here's the statement of the problem. I have an installation where the DBA wants to upgrade all of his MSSQL2000 servers to 2005. I am testing the feasibility of that. The TS event subsystem and the OD scheduler db are both happy. DataDeploy is mostly happy, but not happy enough.
I have a comparison deployment for synchronizing everything. It has four separate datadeploy legs for various data types. Three of those are succeeding. One is failing with the rather cryptic message:
DBD: SQLException occured in TDbSchemaGroupCfg< p O
<> Exception Message: XXXCORP0\INTEGRATIONThe incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 10 (""): Data type 0x32 is unknown.< p O<>
< p O<>< p O<>< p O<>< p>< p>
I've googled and haven't found that exact error yet. The closest I've found is this:
http://support.microsoft.com/kb/915834which seems like it could be a likely culprit. In my case, I'm using the microsoft-inetuna for the DataDeploy, not the microsoft-microsoft driver, so the scenario is not exactly the same. Moreover, since DD actually runs in a separate JVM, I don't think it has the same CLASSPATH as the main instance of OD, so it may not in fact be loading the SQL2005 driver at all.
My preferred path forward would be to get the microsoft-microsoft driver to load the SQL2005 driver. Does anyone know if that is even possible? I remember that back in the days when DB2 7.1 was a supported db and 7.2 was not that one could replace the 7.1 driver jar with the 7.2 driver jar and everything would be peachy. However, I wouldn't expect that to work with MSSQL because they went from three driver jars down to one, and they changed the format of the connection string.
