Posted by Erland Sommarskog on 02/13/07 22:10

Mork69 (mleach@bigfoot.com) writes:
> The only reliable way to catch all issues is to script out your SQL
> 2000 databases and then rebuild them on a SQL 2005 database with
> compatibility level 90. This method is much better than using the
> Upgrade Advisor alone.

I agree that running the scripts is a good idea, because you can
catch all compilation errors.

However, for the actual migration, I strongly recommend to use
backup/restore or detach/attach. Scripting is a more complex and a
process more prone to errors.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]