May 6, 2009 at 7:07 am
Hi,
I'm trying to move dimensional data from a table in a SQL Server Source DB (let's call it 'A') to a SQL Server Destination DB ('B'). The collation of both databases is Thai_CI_AI. The tables have the same collation as the databases.
The columns in both the tables are:
DEPTCODE VARCHAR(50)
DEPTNAME VARCHAR(!00)
The DEPTNAME column in the source database contains records both in English as well as in Thai. In fact, some records even contain a mixture of English and Thai data.
When I try migrating this data from an OLE DB Source to an OLE DB Destination, I'm getting this error: "Text was truncated or one or more characters had no match in the target code page.". This error occurs at the OLE DB Source. Typically, I should not be facing this error because both databases have the same collation, datatypes and column sizes.
I also dragged in a Data Conversion transformation intending to convert the columns to NVARCHAR (making necessary changes in the destination, of course), but I'm getting this error even before it goes to this transformation.
I then dragged in a Data Conversion transformation at the end of the OLE DB Source Error Output, followed by an OLE DB Destination. The data now gets stored, but all the Thai characters are stored as question marks (Eg: 'Department ????').
I finally added a Data Viewer Grid to the OLE DB Source Error Output to see what data is being passed by the OLE DB Source Error Output to the Data Conversion transformation, and it shows me 'Department ????' again instead of proper Thai data.
This means that even though the OLE DB Source Preview shows proper Thai characters, data with question marks is being sent from the OLE DB Source Error Output to the Data Conversion transformation.
As for settings, I have changed the LocaleID to Thai. The DefaultCodePage is set to 874 (Thai), and AlwaysUseDefaultCodePage is set to False.
I'm not sure if this is important, but when I did this on SQL Server 2005 a few months back, I had absolutely no problems.
It'd be great if someone can help me with a solution to this problem.
Regards,
Guru
May 7, 2009 at 11:43 pm
Dear all,
I resolved the issue. I changed the LocaleID from Thai to Thai(Thailand), and made the regional settings (Standards & Formats setting) to Thailand. It worked fine after that!
Regards,
Guru
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply