May 9, 2013 at 9:24 am
Greetings,
We are going to a new server (Windows Server 2012) with SQL 2012 from SQL 2005. We have the DB2 client installed and a linked server configured in order to use OpenQuery to import data, which we do using SSIS. The problem is that, in the new environment, all the string data is now being seen as Unicode. This creates a huge hassle updating the dataflow tasks in the import package by having to add a Data Conversion transform and re-map all the fields.
Does anyone intimate with the DB2 client and SQL Server 2012 know of a setting or change in the DB2 client or linked server configuration in SQL Server 2012 that might cause this change?
I am not the one who installed the client or configured the linked server and so want to pass along anything I can to our DBA folks to get this resolved.
Thanks.
May 14, 2013 at 11:22 am
Which DB2 client are you working with, IBM? Have you tried Microsoft's OLEDB provider for DB2?
http://www.microsoft.com/en-us/download/details.aspx?id=29100
Tommy
Follow @sqlscribeViewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply