SSIS: Codepage Conversion

RudiRutscheRudiRutsche Member Posts: 30
edited 2009-03-27 in SQL General
Hey everybody!

Is it possible to convert textdata from Codepage 1252 (Euro Windows Standard) to Codepage 850 (OEM Latin 1, the codepage NAV uses) using Sql Server Integration Services?

I tried to import Data from a text flatfile using SSIS into a NAV Database (Yes, I know that there are dataports :wink: )

I tried to convert the Data from CP 1252 to 850 with a "Dataconversion" Element, but all i get is an error which says that
"transformation from Codepage 1252 to 850 is not supported"

There has to be a way to convert the data with SSIS I believe.
Does anyone ever did something like that?

Comments

  • dmccraedmccrae Member, Microsoft Employee Posts: 144
    You can create your NAV database using an ANSI code page (such as 1252 in your case) then there is no need for conversion. All Windows Collations use ANSI code pages, and some SQL collations do too. You don't need to use an OEM code page for the database.

    Just thought I'd add: NAV does not specifically use OEM 850. C/SIDE does internally use the machine OEM code page, but the actual code page itself depends on your computer's windows system locale (can be 850, 437, 936 and son on), just as the ANSI code page also depends on this - 1252, 1253, 1257 etc..
    Dean McCrae - Senior Software Developer, NAV Server & Tools

    This posting is provided "AS IS" with no warranties, and confers no rights.
  • RudiRutscheRudiRutsche Member Posts: 30
    Thanks for answering.

    The databases I work with use copage 850, so I have to deal with this.
    We have some quite good NAV functions to convert from ansi to oem, so i would be able to transform the data after importing it.
    The thing is, that i would like to speed up importing processes using SSIS and i was sure such a big "tool" for data conversion would be able to do such a "standard" transformation... :roll:
Sign In or Register to comment.