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 |
|
sqln3wbi3
Starting Member
4 Posts |
 Posted - 2009-06-15 : 09:30:41
|
| Hey all,I've been given the task of upgrading an old SQL Server 2000 database to SQL Server 2005. However, the database itself has already been migrated to a SQL 2005 server AND is NOT running in SQL 2000 compatibility mode (i.e., it's running in the 90 compatibility level [SQL 2005]).Anyways, I've been told that no upgrade work has been done on the database itself to make it fully compatible. I've tried running the SQL Server 2005 Upgrade Advisor and it refused to scan the database. Is there any easy way of figuring out what needs to be changed to make the database fully compatible with SQL Server 2005?Thanks. |
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2009-06-15 : 11:54:18
|
| you cannot run the upgrade advisor on 2005 server... so if you still have the old 2000 server and a 2000 backup of the database, restore it on the 2000 server and run the Upgrade Advisor against it..Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
 |
|
|
sqln3wbi3
Starting Member
4 Posts |
Posted - 2009-06-15 : 11:59:23
|
| I realized that. Is there no other way of checking what needs to be upgraded though? A tool, script, something? I don't have access to the old 2000 server nor do I know if a 2000 backup exists. |
|
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2009-06-15 : 14:47:32
|
| you can script out and migrate all the objects to some 2000 server and run the UA against it.. at least you can find out if there is any syntax that will break...Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2009-06-15 : 15:25:05
|
If you already are running the database with SQL Server 2005, and the compatibility level is set to 90 and evertything works, yes, the application is SQL Server 2005 compliant.
E 12°55'05.63"N 56°04'39.26" |
|
|
|
|
|
|
Making DB fully SQL 2005-compatible