Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Question: How do I pervent Chinese characters from turning into ? (SSIS 2008R2) Expand / Collapse
Author
Message
Posted Friday, April 11, 2014 7:52 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 18, 2014 10:12 PM
Points: 358, Visits: 1,066
Ok, I've been confronted by this problem during the week where I'm the only guy not on break on our SQL team.
I got a series of databases that have data concerning clients in Asia,now this week (about 3 months after go live) we get the report the Chinese characters have turned into ?

The source is an IBM DB2 UDB for iSeries IBMDASQL OLE DB Provider,in the preview the characters are shown correctly but they turn into ? as soon as they leave the source.
The fields are string [DT_STR] codepage 1252,here lies the problem,this causes the Chinese characters to be turned into ?.

However when I change it to unicode type,the package errors on the source. Is their any solution for this.
Post #1560931
Posted Friday, April 11, 2014 8:19 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 5,317, Visits: 12,355
Resender (4/11/2014)
Ok, I've been confronted by this problem during the week where I'm the only guy not on break on our SQL team.
I got a series of databases that have data concerning clients in Asia,now this week (about 3 months after go live) we get the report the Chinese characters have turned into ?

The source is an IBM DB2 UDB for iSeries IBMDASQL OLE DB Provider,in the preview the characters are shown correctly but they turn into ? as soon as they leave the source.
The fields are string [DT_STR] codepage 1252,here lies the problem,this causes the Chinese characters to be turned into ?.

However when I change it to unicode type,the package errors on the source. Is their any solution for this.


What exactly are you changing when you 'change to Unicode type'?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1560956
Posted Friday, April 11, 2014 8:29 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 18, 2014 10:12 PM
Points: 358, Visits: 1,066
Phil Parkin (4/11/2014)

What exactly are you changing when you 'change to Unicode type'?


I go into the advanced editor and change the datatype of the column
Post #1560966
Posted Friday, April 11, 2014 8:52 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 5,317, Visits: 12,355
Resender (4/11/2014)
Phil Parkin (4/11/2014)

What exactly are you changing when you 'change to Unicode type'?


I go into the advanced editor and change the datatype of the column


Can you post the error message?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1560983
Posted Friday, April 11, 2014 9:00 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 18, 2014 10:12 PM
Points: 358, Visits: 1,066
When trying to execute with the colums put on unicode, via advanced editor
TITLE: Package Validation Error
------------------------------

Package Validation Error

------------------------------
ADDITIONAL INFORMATION:

Error at Pull [Source [1]]: The output column "VNDNAM" (1294) on the error output has properties that do not match the properties of its corresponding data source column.

Error at Pull [SSIS.Pipeline]: "component "Source" (1)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".

Error at Pull [SSIS.Pipeline]: One or more component failed validation.

Error at Pull: There were errors during task validation.

(Microsoft.DataTransformationServices.VsIntegration)

------------------------------
BUTTONS:

OK
------------------------------

------------------------------------------------------------------------------------------------------
TITLE: Editing Component
------------------------------

The component is not in a valid state. The validation errors are:
Error at Pull [Source [1]]: The output column "VNDNAM" (1294) on the error output has properties that do not match the properties of its corresponding data source column.


Do you want the component to fix these errors automatically?

------------------------------
BUTTONS:

&Yes
&No
Cancel
------------------------------

Post #1560992
Posted Sunday, April 13, 2014 1:36 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 5,317, Visits: 12,355
Did you modify the datatype of the column in both 'External Columns' and 'Output Columns'?


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1561294
Posted Monday, April 14, 2014 1:41 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 18, 2014 10:12 PM
Points: 358, Visits: 1,066
Phil Parkin (4/13/2014)
Did you modify the datatype of the column in both 'External Columns' and 'Output Columns'?

yes I changed them both from string DT_STR to DT_WSTR & that leads to the aforementioned error message
Post #1561354
Posted Monday, April 14, 2014 3:00 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 5,317, Visits: 12,355
Resender (4/14/2014)
Phil Parkin (4/13/2014)
Did you modify the datatype of the column in both 'External Columns' and 'Output Columns'?

yes I changed them both from string DT_STR to DT_WSTR & that leads to the aforementioned error message


And are you directing errors somewhere else? Have you also checked the error output?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1561378
Posted Monday, April 14, 2014 5:03 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 18, 2014 10:12 PM
Points: 358, Visits: 1,066
There no error message except for the validation error,cause that stops the execution of the rest of the package
Post #1561429
Posted Monday, April 14, 2014 5:11 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 5,317, Visits: 12,355
Resender (4/14/2014)
There no error message except for the validation error,cause that stops the execution of the rest of the package


I mean are you redirecting error rows - have you checked the error output?

Like this, I mean.



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1561431
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse