Hey Qaryplum,
There are more then a few ways to do it. For moving Database you might
not face much of hassle. The way I started doing it is by:

1) detach / take one db offline
2) copy database files (mdf,ldf,ndf,etc)
3) attach to new sql2005 box.
4) after all db xfer, move users either with SSIS/Dts task (this moves
without user passwords) or by the famous Microsoft kb article
(http://support.microsoft.com/kb/246133).

After this comes the hard part the dts. For that you can:
1) Leave dts running on old sql2000 box while referencing the new db
2) Migrate the DTS to SSIS, (usually wizards does the simple dts
migration for you except few analysis service tasks and Activex tasks).

Hope that I helped.

Thanks.
FP

-----Original Message-----
From: garyplum
[mailto:mssqldba-ezmlmshield-x51971946.[Email address protected]
Sent: Friday, November 30, 2007 14:59 PM
To: LazyDBA Discussion
Subject: 2000 to 2005 upgrade

Hi

I've been asked to upgrade a SQL 2000 box of ours to SQL
2005 (most of our boxes run 2005); running Win2003 Enterprise Server.



Do I need to disable replication first & what are the major 'Gotha's' to
be ready for?



I intend leaving the 2000 DTS packages alone until I get my breath back
:-)



The upgrade advisor has flagged a few issues but nothing huge!!!



Best regards

Gary





---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


MS Sql Server LazyDBA home page