Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
Options
SQL Collation and Codepages
ta5
Member Posts: 1,164
Hi
We have a strange behaviour and I shall be happy if somebody could shed some light on it...
The story is to convert a native db into sql 2008r2. After checking the date fields in native and backing up, the nav restore fails because of invalid characters in customer table (character š = alt+0154). When I uncheck the checkbox "validate codepage" the nav restore on sql works, but thats not we want to do.
The server and the client where the native backup was coming from and the destination sql server have the same code page settings. In the "change database" settings the collation is set to windows. When I set to sql collation (type 41) it also works, but as far as I understand the installation guide sql collation should not be taken.
I'm interested on some theory about that, especially why the change from windows collation to sql collation makes the difference. Other question is, whats best practice regarding these topics when planning a migration to sql?
Thanks in advance.
Thomas
We have a strange behaviour and I shall be happy if somebody could shed some light on it...
The story is to convert a native db into sql 2008r2. After checking the date fields in native and backing up, the nav restore fails because of invalid characters in customer table (character š = alt+0154). When I uncheck the checkbox "validate codepage" the nav restore on sql works, but thats not we want to do.
The server and the client where the native backup was coming from and the destination sql server have the same code page settings. In the "change database" settings the collation is set to windows. When I set to sql collation (type 41) it also works, but as far as I understand the installation guide sql collation should not be taken.
I'm interested on some theory about that, especially why the change from windows collation to sql collation makes the difference. Other question is, whats best practice regarding these topics when planning a migration to sql?
Thanks in advance.
Thomas
0
Answers
Again, main thing is that you need to use correct language for non-unicode applications on your computer when making/restoring the backup. In this case, if I am correct, Czech one...
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Thanks for replying. Well, its a czech character, but its a swiss database, but the name of the customer seems to be czech and so this character found its way to the "search name". Does it make a different whether the value is in a normal field or in an indexed field?
Anyway, I'm still unsure about the correct solution, because setting non unicode codepage to czech, maybe there might another field in the db from another character set...
Thanks in advance for your comments.
Thomas