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
- 298 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
Latin-1 and Cyrillic in the same DB: native OK, SQL not?
Miklos_Hollender
Member Posts: 1,598
Strange that it was not discussed much here, searched mibuso and no definitive answer... it must be a common scenario: Western company has a subsidiary in Russia, Ukraine or Serbia. Can they have them as a company in the same database?
In native yes, tested, works.
But in SQL there will be, I think a problem with the collation.
I even heard a rumour that you can't even have them on the same server in SQL... not sure why, as you don't necessarily have to use Windows collation, do you?
Anyone have some experience in this?
In native yes, tested, works.
But in SQL there will be, I think a problem with the collation.
I even heard a rumour that you can't even have them on the same server in SQL... not sure why, as you don't necessarily have to use Windows collation, do you?
Anyone have some experience in this?
0
Comments
One of My customer have one database for Holland, England and Poland offices
After uncheck "Validate code page" on "collation" tab in "alter database" it works fine, and every user can use his special character in database.
I remember there was a problem after changing this option in not empty database. (but maybe this problem was after changing collation descpription...im not sure about this)
Database is crush after this because in some tables some records have the same "primary key" after job is done.
So before changing this one better check for "special characters" in primary key in tables and rename.