|
|
Posted by Mork69 on 02/14/07 09:58
On Feb 13, 10:10 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> Mork69 (mle...@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, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
In fact, if both approaches are used then the migration should be
perfect. i.e. You script out and build in order to highlight and fix
all the problems. If you keep the scripts for the objects that were
fixed then you can do the detach/attach and then recreate them.
Navigation:
[Reply to this message]
|