Changing Codepage on NAV SQL Database

RobbieX
RobbieX Member Posts: 66
edited 2010-01-07 in NAV/Navision Classic Client
Does anyone know what the consequences may be of Changing the Codepage on a NAV SQL Database?
We are using NAV 5 SP1 SQL option and want to pass and receive data between NAV and another application both using SQL databases.
We need to receive Chinese characters in a NAV staging table so that it can be processed, but if we keep the codepage as Latin or Western then the Chinese characters that are inserted from outside NAV are illegible.
Likewise, if NAV places Chinese data in a staging table it is illegible for the other application.
If we change the codepage of the database to Simplified Chinese however (from SQL Management Studio) NAV can read the characters correctly and so can the other application.
We noticed that the NAV backup and restore functionality does not work any longer but we can always use SQL backups.
Could anything else in NAV be terribly effected?
I would appreciate any advice. Thanks!
Robbiex

Comments

  • Marije_Brummel
    Marije_Brummel Member, Moderators Design Patterns Posts: 4,262
    If this is your critical business application I would not do this if it is not supported.

    Using the staging table is the best approach and you should be able to convert the characters from within SQL Server statements.

    There is a unicode conversion tool available as download on www.dynamicsusers.org. Maybe you should investigate that.

    In NAV you are only allowed to use the codepages in your stx file. There is a support for simplified chinese AFAIK with a special stx file. Contact your NAV partner to have support on this.
    Marije Brummel | Freelance Business Central Specialist

Categories