SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Working with unicode (UTF-8)


Working with unicode (UTF-8)

Author
Message
schep021
schep021
SSC Eights!
SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)

Group: General Forum Members
Points: 832 Visits: 770
We have a large amount of jobs that take data from our Oracle database, transform it, and then import it into or SQL Server databases. We recently changed our Oracle, source, database from WIN1252 to UTF-8. This has broken our SSIS packages and producing multiple errors with ..."cannot convert between unicode and non-unicode"...

Changing the source back to WIN1252 is not an option.

I believe we may have found a work around by adding a data conversion task within the package. But, there are over 500 hundred packages and mapping each column within each package will be VERY time consuming. (http://msdn.microsoft.com/en-us/library/aa337316%28v=SQL.90%29.aspx)

Has anyone tried this work around before? Have you had any issues? I am worried about invalid characters, truncation, and the effects on performance.

I was looking into updating all the destination tables to only have unicode columns (nvarchar, nchar, etc) to see if I could do a direct import if the columns were large enough. But, from what I read, translations will not match.

We are running SQL Server 2005 SP2.

Thank you for your time!
schep021
schep021
SSC Eights!
SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)SSC Eights! (832 reputation)

Group: General Forum Members
Points: 832 Visits: 770
I was able to create a new table using the import/export wizard. The wizard was nice as it created the correct columns needed in order to hold the unicode data. I have read that SQL Server stores unicode in UCS-2 encoding schema, and the source was UTF-8. So, I'm unsure if there will be issue there. Has anyone taken this approach? Will the difference between encodings cause issues?
Jo Pattyn
Jo Pattyn
SSCertifiable
SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)

Group: General Forum Members
Points: 6949 Visits: 10009
Not sure if following links helps as they are directed to sqlplus regarding unicode
Interesting link on Oracle unicode
SQL Snippets: unicode - unicode and SQL*Plus (Windows)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search