Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ostinoh
Yak Posting Veteran
66 Posts |
 Posted - 2010-04-13 : 14:11:17
|
| Hello - I currently have a few of my databases set with the Compatibility Level set to SQL Server 2000 (80) on SQL Server 2005.Can someone please help me understand what are the dangers of changing that to SQL Server 2005 (90) if any?Regards,Ostinoh |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
ostinoh
Yak Posting Veteran
66 Posts |
Posted - 2010-04-13 : 14:50:13
|
| Very true... Thank you for the fast response. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-04-13 : 15:39:25
|
| If you are migrating from SQL2000 / Compatibility mode 80 to SQL2005 (90) - or SQL2008 (100) then I recommend you check this thread:http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=138230&SearchTerms=sql2008,tipsit relates specifically to SQL2008, but most of the issues are relevant to SQL2005 / Compatibility mode 90 too - such as changing the PAGE_VERIFY method to give you the earliest possible warning if (When?!!) data corruption occurs, and use of Database Upgrade Advisor which may point out things that you need to change as part of the migration upgrade.Also, if you are only now planning to migrate to SQL2005 native mode (Compatibility mode 90) and faced with making a complete regression test to ensure that everything works "just fine", which is surely going to cost the business many $x,000, I would urge you to consider upgrading to SQL2008 instead - that way you only have to make the Regression test once but you safeguard your application for several more years, whilst also being able to take advantage of the new features specific to SQL 2008. |
|
|
|
|
|
|
Change Database Compatible Level???