[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Upgrade/Downgrade SQL Server Compatability Level

Posted on 2015-01-29
6
Medium Priority
?
298 Views
Last Modified: 2015-01-30
We have an old app that is running on SQL Server 2005 and the database is set to compatibility level 80 (SQL 2000).  Would like to change to level 90 (SQL 2005).  If problems surface, can we simply change back to level 80? (assuming we don't make use of any new features).  Can the compatibility level be changed back and forth until all problems are worked out?  The database will stay on the same server that is running 2005 binaries.
0
Comment
Question by:ralicea
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
6 Comments
 
LVL 80

Assisted Solution

by:arnold
arnold earned 800 total points
ID: 40578370
Yes, the compatibility mode alters how the database is accessed on the same server,
properties of DB, options.
The DB is already in sql 2005 schema.
Compatibility alters which "features" are available.


Why not use a separate test environment where you can weed out the issues?

Let me tell you that while making this change will likely have minimal impact if at all, any issue will be blamed on this change.

i.e. you tell someone you do X on system A.  Any issues that come up with system A will be referred to you to fix given the presumption that since you did X, your change is the cause for the issue.
0
 

Author Comment

by:ralicea
ID: 40578381
We have a test environment and will test as best as possible.  Just want to be sure that if we do miss something and the level is changed in production, we can "downgrade" the compatibility level to solve the immediate problem.
0
 
LVL 80

Expert Comment

by:arnold
ID: 40578414
The effect of comaptibility mode is similar to a four wheel drive vehicle that has a drive train selector (front or rear, front and rear low, front and rear hi)
The action deals with altering DB so if it is an active DB, it might have a slight impact.

certain features available in sql 2005 mode, are not available in sql 2000 compatibility mode.
https://msdn.microsoft.com/en-us/library/ms191137%28v=sql.90%29.aspx

My suggestion, is to test in your test environment as though there is no going back.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 52

Expert Comment

by:Vitor Montalvão
ID: 40579254
When you migrated the database from MSSQL 2000 to 2005 you didn't run the upgrade advisor first?
After changing the compatibility level to 90 you need to run the following command:
DBCC CHECKDB ('DatabaseNameHere' ) WITH ALL_ERRORMSGS,NO_INFOMSGS, DATA_PURITY

Open in new window

And yes, you can set back the compatibility level to 80.
0
 

Author Comment

by:ralicea
ID: 40579781
I inherited the database and application so I don't know if upgrade adviser was run prior.  What I have is SQL 2005 binaries running a database in 2000 compatibility.  I've searched the code for known problems and believe I've found and corrected them.  I'm getting ready to change the comparability mode but want to fully understand the ramifications and roll back options.  I want to be certain I can simply change the compatibility mode back if an unforeseen problem arises or will I have to do a restore and reapply data changes.
0
 
LVL 52

Accepted Solution

by:
Vitor Montalvão earned 1200 total points
ID: 40579797
I've searched the code for known problems and believe I've found and corrected them.
Good. It's one of the things the upgrade advisor does but it can only check the code inside SQL Server (SP's, functions, triggers,...).

want to be certain I can simply change the compatibility mode back if an unforeseen problem arises or will I have to do a restore and reapply data changes.
Yes, you can set back the compatibility mode but having a backup ready to be restored is always wise.
0

Featured Post

Enroll in October's Free Course of the Month

Do you work with and analyze data? Enroll in October's Course of the Month for 7+ hours of SQL training, allowing you to quickly and efficiently store or retrieve data. It's free for Premium Members, Team Accounts, and Qualified Experts!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
What if you have to shut down the entire Citrix infrastructure for hardware maintenance, software upgrades or "the unknown"? I developed this plan for "the unknown" and hope that it helps you as well. This article explains how to properly shut down …
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Via a live example, show how to shrink a transaction log file down to a reasonable size.

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question