Special/Foreign Language Characters Issue

Hi,
 
We have a package that does a simple table to table data loading. Both source and destination have the same Codepage (850) and collation (SQL_Latin1_General_CP850_CI_AI). However, there are some foreign language characters in the source table, and it gets messed up when it's loaded into the target.
 
Here's an example for a column with this type of text:
 
Source: Solut§es Informst
Target: Solu■oes Inform t
 
Both columns are char(30).
 
I have tried to load this row into another server in a different location and it works just fine, however the original target of data displays the text incorrectly.
 
I have no idea what can be causing this.
 
Thanks,
Kervy


Answer this question

Special/Foreign Language Characters Issue

  • mfdiqwer

    hi Enric,
    yes I found that odd as well. the ascii values are different for what was really displayed.. I'm really baffled by it but I don't think it has anything to do with my problem, just an odd finding.
    Hi Wenyang,
    I'm using package configurations to set the connection string to both the source and target. In my configuration, the configured values for the connection strings look like this -
    Data Source=<server>;User ID=<username>;Password=<password>;Initial Catalog=<database>;
    Autotranslate isn't explicitly set in the package configuration as you can see. But just to check, I opened the package in the designer and checked the connection manager for both source and target and they have autotranslate set to true. Does autotranslate affect the loading of data in any way do I have to set it to true/false in the package configuration
    Thanks,
    Kervy

  • GranBosco

    Source: Solut§es Informst
    Target: Solu■oes Inform t
    Maybe is spanish language
    Solut§es Informst = Soluciones Informaticas


  • xRuntime

    Kervy
    In your target connection, is Auto Translate true or false How about that in the source connection

    thanks

    wenyang



  • hitparader

    I just set auto translate = False in my configurations and it worked! However, I still don't understand how I was able to deliver the correct data to a different server using my original configuration.
     
    ok I have just confirmed that auto translate = false really fixed my problem. I would like to thank Wenyang for mentioning Auto translate which made me investigate about that matter. I think the client's code page is different from that of sql 2005 and so auto translate should be set to false, otherwise there will be a loss of data or possible corruption hence it won't be displayed correctly.
     
    For others who might have a similar problem, you can check this out - http://support.microsoft.com/ scid=http%3a%2f%2fwww.support.microsoft.com%2fkb%2f904803%2f
     
    Thanks guys,
    Kervy

  • mail2amar

    hi,

    This is a special character: §, but curiously it appears with 21 and 245 code in ASCII table

    how odd!



  • skynes

    Hmmm anyone

  • Special/Foreign Language Characters Issue