SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Compatibility level 80 Vs 90 - SQL Server 2005


Compatibility level 80 Vs 90 - SQL Server 2005

Author
Message
river1
river1
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: General Forum Members
Points: 11488 Visits: 1737
Hi,

Some of the people that work with me on the company convert a database from SQL Server 2000 to SQL Server 2005 without even changing the comaptibility level.

They just do backup on SQL Server 2000 and restore the database on SQL Server 2005.

I always change the compatibility level to 90 and change the error detection from torn page detection to CheckSum.

I would like to tell them why is good for them to change the database compatibily level to 90, but i am not choore. I know that if the database is in compatibility level 80 it works in backword compatibility level, but that affects the performance of the database or can cause any damage?


Thank you
Lowry Kozlowski
Lowry Kozlowski
Ten Centuries
Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)

Group: General Forum Members
Points: 1000 Visits: 508
Having converted many databases from SQL2000 via backup and restore and running on SQL2005, changing compatablility is relatively low on my scale of things that need to be changed. I have a mixed bag of compatablilties on my production 2005 boxes and the ones set at compatablity 80 vs 90 perform no differently.

The reason we didn't change them is due to some of the older 3rd party tools they were utilizing. We didn't want to break anything, and once you change the compatiblity you cannot go back.

I agree about the checksum change. That would be higher on the priority list to be changed.
river1
river1
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: General Forum Members
Points: 11488 Visits: 1737
"I agree about the checksum change. That would be higher on the priority list to be changed"

but you can only change the to checksum if you are in compatibility level 90?
Lowry Kozlowski
Lowry Kozlowski
Ten Centuries
Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)Ten Centuries (1,000 reputation)

Group: General Forum Members
Points: 1000 Visits: 508
You can change the Page_verify_option to Checksum on compatibility 80 without going to 90

SELECT name, create_date, compatibility_level,user_access_desc,state_desc, recovery_model_desc,page_verify_option_desc FROM sys.databases

This is just a quick way to gather that info for you
steveb.
steveb.
One Orange Chip
One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)

Group: General Forum Members
Points: 25706 Visits: 7195
I would never automaically change the compatability level ot 90 after an upgrade as there is too big a risk that some application will fail to function in Level 90.

Test first, then change the level if required.
river1
river1
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: General Forum Members
Points: 11488 Visits: 1737
" would never automaically change the compatability level ot 90 after an upgrade "

I would never too...

The database will be tested with the app
Jeffrey Williams 3188
Jeffrey Williams 3188
SSC-Forever
SSC-Forever (46K reputation)SSC-Forever (46K reputation)SSC-Forever (46K reputation)SSC-Forever (46K reputation)SSC-Forever (46K reputation)SSC-Forever (46K reputation)SSC-Forever (46K reputation)SSC-Forever (46K reputation)

Group: General Forum Members
Points: 46501 Visits: 10150
Lowry Kozlowski (4/1/2011)
We didn't want to break anything, and once you change the compatiblity you cannot go back.


The compatibility level can be changed back, if needed. When you change this, there is nothing in the database that is upgraded or converted that will prevent you from changing it back.

All this does it tell SQL Server what commands, functions, etc... are available in that database.

Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs

ErikEckhardt
ErikEckhardt
SSC Rookie
SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)

Group: General Forum Members
Points: 30 Visits: 113
The compatibility level can be changed back, if needed. When you change this, there is nothing in the database that is upgraded or converted that will prevent you from changing it back.

All this does it tell SQL Server what commands, functions, etc... are available in that database.

That's not *all* it does. It can change the parsing of queries, their execution plans, and the meaning of certain constructs in queries. It can change sort orders. There's a lot it can cause to happen--but you're right, it doesn't change the data.

I in particular have experienced seeing an application negatively affected by an ordering issue when changing the compatibility level to higher. That the application relied on a particular order without an ORDER BY was poor design; but nonetheless it existed.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search