Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 295 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Changing Codepage on NAV SQL Database
RobbieX
Member Posts: 66
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!
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
0
Comments
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.