Home Forums SQL Server 2012 SQL 2012 - General SSIS issues after changing servers with character sets or code page or whatever its called RE: SSIS issues after changing servers with character sets or code page or whatever its called

  • August 23, 2017 at 6:40 pm

    #1956530

    Dave C. - Friday, August 18, 2017 1:52 PM

    I am having my ssis package fail when converting characters not supported by our iseries.  This package used to run fine on Windows 2008 svc pack 2 but now failing once switched to run on windows server 2012 R2 and I can't figure out how to resolve. 

    Someone suggested it is with different code pages or collation or regional settings etc which I know nothing about.  I am just trying to determine where to look on both servers to find the difference and make the 2012 the same as the 2008 R2 was.   I'm a developer not a system guy as you can probably tell so not sure of terminology etc.  I do have access to both systems so I can look at whatever I need to if I knew what that was.

    I'm hoping someone can tell me what I'm looking for and where it is on both systems.  Thanks!

    Regional settings - go to control panel and then Regional and Language settings. Refer to this -
    How to: Change Operating System Settings to Support Localized Versions

    To find the code page being used - open the command prompt as administrator, type in chcp and it will report the code page.
    Refer to this to see what the values are:
    Code Page Identifiers

    To get database collations, you can use this:
    select name, collation_name
    from sys.databases

    I wouldn't change anything if you find any differences though.
    What is not working? You said "converting characters not supported by our iseries". Converting from where to where and which is failing? Are you importing to iseries, exporting to iseries, from where to where? It may not have anything to do with what was suggested and you could definitely hose out more than your SSIS packages.

    Sue