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

SSIS File Import Collation Expand / Collapse
Author
Message
Posted Tuesday, March 09, 2010 12:32 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, September 20, 2011 6:48 PM
Points: 7, Visits: 52
I am using SSIS to import text files, which include french accented characters in some fields, from a remote database into a local database. Table structures, collation, etc., are identical in local and remote databases.

The collation on the target database is set to Latin general 1252. There is no problem storing the data in the current varchar fields (not nvarchar), in either the source or target databases, of course.

Here is the problem. When I set up the file connector, I can only see the french characters properly if I use UTF8 collation. Otherwise I get odd character substitutions. however, in this setup, the ole db destination object complains about "more that one codepage specified...".

I am guessing (hoping) that there is something simple I am missing to make this work.

My question is: what is the simplest way to pull in the file data correctly (which looks like I will need to use unicode, or utf-8), but then pass that data back to the ole db destination object which is connecting to the 1252 codepage database?

Thanks in advance for any suggestions.

Paul
Post #879639
Posted Thursday, January 05, 2012 8:06 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 04, 2014 5:58 AM
Points: 1, Visits: 28
I just had the same issue myself and managed to get around it by using 2 data conversion tasks.

The first to convert UTF-8 data read from the file to unicode
and then the second to convert from unicode to correct code page. 1252 in my case

Has to be a 2 step process because it will not let you convert directly from UTF-8
Post #1230787
Posted Friday, March 15, 2013 8:54 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, December 03, 2013 8:47 AM
Points: 1, Visits: 40
Hi...I am havig the same problem but I dont know if I understood I added the 2 data conversions as you said but I am getting the same problem. I am missing the accent SQL adde + signs instead of the french accent.

I added one data conversion as Unicode string an the other as STRINg 1252. Let me know if I am doing something wrong.

Thanks
Post #1431575
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse