Hi All, I have a SQL Server data source that has a collation of Chinese_PRC_CI_AS and the columns has VarChar datatypes. My destination Database also has a collation of Chinese_PRC_CI_AS and the destination column for the Chinese character has NVarChar datatype. On SSIS, I created a simple dataflow that consist of OLEDB Source, Lookup, Data Conversion, and OLEDB Destination. But when the loading is finished, the Chinese Character has turn into unreadable text. My initial thinking could be the Data Conversion that i have used. I use Data Conversion to convert from STR to WSTR datatype, so that I can map the Source Column to the Destination Column that has an NVarChar datatype. Can anyone help me. Thanks in advance.

Have you tried setting the code page property of the OLEDB source (in "Advanced Editor") to an appropiate value (950?).(Twitter | Blog)

Hi I tried your suggestion but still no luck. Thanks.

In your Source OLE DB in the select statement try converting the column to NVARCHAR. SELECT CAST(yourChineseColumn AS NVARCHAR(<Length>)) AS yourChineseColumn FROM YourTable So you don't need the conversion. You might want to try to recreate the OLEDB Source to correct the data type or manually adjust it using advance editor if there's some problem.Randy Aldrich Paulo MCTS(BizTalk 2010/2006,WCF NET4.0), MCPD | My Blog BizTalk Message Archiving - SQL and File Automating/Silent Installation of BizTalk Deployment Framework using Powershell > Sending IDOCs using SSIS

In your Source OLE DB in the select statement try converting the column to NVARCHAR. SELECT CAST(yourChineseColumn AS NVARCHAR(<Length>)) AS yourChineseColumn FROM YourTable So you don't need the conversion. You might want to try to recreate the OLEDB Source to correct the data type or manually adjust it using advance editor if there's some problem.Randy Aldrich Paulo MCTS(BizTalk 2010/2006,WCF NET4.0), MCPD | My Blog BizTalk Message Archiving - SQL and File Automating/Silent Installation of BizTalk Deployment Framework using Powershell > Sending IDOCs using SSIS

In your Source OLE DB in the select statement try converting the column to NVARCHAR. SELECT CAST(yourChineseColumn AS NVARCHAR(<Length>)) AS yourChineseColumn FROM YourTable So you don't need the conversion. You might want to try to recreate the OLEDB Source to correct the data type or manually adjust it using advance editor if there's some problem.Randy Aldrich Paulo MCTS(BizTalk 2010/2006,WCF NET4.0), MCPD | My Blog BizTalk Message Archiving - SQL and File Automating/Silent Installation of BizTalk Deployment Framework using Powershell > Sending IDOCs using SSIS