August 15, 2007 at 11:04 am
Hi All,
I recently upgraded a SQL 6.5 box to SQL 2000 using the Upgrade Wizard. I noticed 2 weeks later that it has left the new db in 65 Compatibility mode.
Is this normal?
Other than the inability to use 2K features not compatible with 65, does it hit overall performance?
Is it only Stored Procs and Views that would be affected by a switch to 80 Compatibility Mode?
For example, I have a table that I want to change the char of a field from 10 to 15. I can't use the Alter Database Alter Column command as it does not work in 65 mode. Instead I'm gonna have to script a new table, dts data, drop table, recreate, dts data bla bla bla (and therefore do so out of hours!)
August 15, 2007 at 11:14 am
Yes, it's normal for it to stay in the earlier compatibility mode in my experience. If you update it to compatibility mode 80 it will open up the ability for the database to utilize all the features of SQL Server 2000 including updates to the supported T-SQL language (i.e. ALTER TABLE/ALTER COLUMN...).
August 15, 2007 at 1:41 pm
As a general rule, unless there were features in 6.5 that were deprecated in 7 and then dropped in 2000, you run the risk of using deprecated features from 6.5 in some of your activities. However, in most cases these would be optimization features that no longer optimize in any event (and I don't know if they would work even with a compatibility setting of 65).
Make a test copy of your database and try it. I believe you can still find a the M$ webpage which identifies what's new in 2000 and what's deprecated in 2000. That will give you a conceptual framework. If nothing is deprecated, then you are home free!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply