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
Is there any dangers in Changing Compatibility Level?
slmaluwa
Member Posts: 366
A customer is deploying a new server (Win2K8 (x64)R2 and SQL 2K8 (x64) R2). Their current DB is on win 2003 with SQL 2005 all x32. (NAV 5.0 SP1 clients with tech upgrade from 4.0 SP3 db)
I just restored the DB to new server and tested. All seem to work fine. Now, i am about to change the NAV DB's SQL 2k8 R2 compatible level from 90 to 100.
Has anyone seen any problem in NAV related to this change? is it advisable to change it?
TIA
I just restored the DB to new server and tested. All seem to work fine. Now, i am about to change the NAV DB's SQL 2k8 R2 compatible level from 90 to 100.
Has anyone seen any problem in NAV related to this change? is it advisable to change it?
TIA
"A bove maiore discit arare minor"-"From the old ox, the young one learns to plow."
0
Answers
It is best to change the DB to the latest compatibility level.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
RIS Plus, LLC