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 |
|
AgaK
Yak Posting Veteran
86 Posts |
 Posted - 2010-01-25 : 14:15:10
|
| Would changing compatibility level from 80 to 90 on a database that was upgraded to SQL 2005 2 years ago cause problems to the application (queries not executing properly)?Thank youAK |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-01-25 : 14:18:13
|
| Maybe--Gail ShawSQL Server MVP |
 |
|
|
AgaK
Yak Posting Veteran
86 Posts |
Posted - 2010-01-25 : 14:30:57
|
| Are there features that existed in SQL 2000 but don't exist in SQL 2005 any more? |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-01-25 : 14:46:36
|
| yes. http://msdn.microsoft.com/en-us/library/ms144262(SQL.90).aspxalso see this: http://msdn.microsoft.com/en-us/library/ms143729(SQL.90).aspx |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2010-01-25 : 14:58:36
|
My $0.02 worth ...... if you change Compatibility Level you need to perform a full regression test.... if you move to a new version of SQL Server you need to perform a full regression test (i.e. whether you change Compatibility Level, or not - who knows whether some new bug / logic flow has crept in)So, given that, IMHO best is to change to the latest Compatibility Level and regression test that, and then you can take advantage of all the latest features in the new SQL version.Check up the Upgrade Advisor (for SQL 2005). If that finds no problems that will give you some comfort the changing compatibility level should be low-risk  |
|
|
|
|
|
|
compatibility level