DB Compatibility Setting 70 - What does this do in MSSQL2000 ??
-
Hello,
What is the result of setting a database compatibility setting of 70 within a MSSQL 2000 environment? What happens? Is it as robust? Pros/Cons?
I have a vendor that is recommending that we move their MSSQL 7 db into MSSQL 2000 but set the database compatibility setting at 70, not 80. The reason being ... parts of their app (web component) are new and require 2000, and the other parts were designed in 7 so hence, migrate it, but set it at 70 "to be safe".
Any thoughts or experiences are greatly appreciated.
Many thanks. Jeff
-
Great question. I know as a rule, this isn't recommended from a performance standpoint as not all performance enhancements available in 2000 are supported. But if your hardware is new and already optimized for SQL Server and you database isn't enormous, I can't imagine this being too big of a deal.
This link might help you some: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_bckwd_3vlc.asp
FWIW, it's 2005 and the vendor hasn't yet certified their database for 2000?
What's up with that? I am not poking fun though...I have an app here where I'm still stuck supporting Win 95 clients 
so I feel your pain. My hovercraft is full of eels.
-
I wouldn't expect any problems leaving compatibility at 80, because there aren't major differences between sql server 7 and sql server 2000.
In 2000 they added user defined functions,changable collations and better use of indexes.
-
Basically, you are 'fooling' your SQL Server 2000 into thinking it's a SQL Server 7 system. The purpose is to allow SQL Server 7 functionality to still work.
-SQLBill
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply