Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 305 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Collation Change
darrenc
Member Posts: 16
Hi All
We have several SQL servers that interface with NAV. All the servers are running on the same collation (SQL_Latin1_General_CP1_CI_AS) with the exception of our NAV database, which is using Latin1_General_CS_AS. I would like to change the NAV database to SQL_Latin1_General_CP1_CI_AS so that it matches our other servers but I don’t see it as an option in the Alter Database dialog in the NAV client. Does anyone know if this is a license issue or some other limitation with NAV? Maybe only certain collations are available with a particular localization (we are using the US localization). Also, any other potential pitfalls that may arise when changing collation that I should be aware of? I know we will have some primary key issues because we are going from a case sensitive to a case insensitive collation.
FYI: Running NAV SP3 – migrating from SQL2000 to SQL2005 at the same time we are changing the collation
Thanks
We have several SQL servers that interface with NAV. All the servers are running on the same collation (SQL_Latin1_General_CP1_CI_AS) with the exception of our NAV database, which is using Latin1_General_CS_AS. I would like to change the NAV database to SQL_Latin1_General_CP1_CI_AS so that it matches our other servers but I don’t see it as an option in the Alter Database dialog in the NAV client. Does anyone know if this is a license issue or some other limitation with NAV? Maybe only certain collations are available with a particular localization (we are using the US localization). Also, any other potential pitfalls that may arise when changing collation that I should be aware of? I know we will have some primary key issues because we are going from a case sensitive to a case insensitive collation.
FYI: Running NAV SP3 – migrating from SQL2000 to SQL2005 at the same time we are changing the collation
Thanks
0