Hi all, I've got a bunch of 2K databases ranging from 10Mb to100Gb in size, with corresponding complexity of DTS packages, numbersof logins/user etc, that will have to come off a 2K box that is to bedecommissioned, and migrated/upgraded to a recently configured 2K5 box. I'm trying to build an overall methodology, here's what I've got so far, it's by no means exhaustive or correctly ordered; 1. Audit datafile sizes, datafile placements, DB options (Autogrow/logfile placement etc); 2. Audit scheduled processes/DTS jobs; 3. Place above info into Excel S/S; 4. Run DBCCâ€™s updateusage and checkdb before the transfer: 5. Set database(s) to Single-User mode 6. If above ok, Backup DB's and attach at target, or use Copy/Transfer DB wizard; 7. Run script at target to check that filesizes/rowcounts etc tally with those before backup, if not review for errors; 8. Runscript to check that DB options identical to those at source, if minordifferences found (ie torn page detection etc) change manually, ifmajor (disk file placement) back out; 9. Run scriptto check that expected users/logins survived migration, if not recreatethese and/or orphans programmatically/graphically (depending of courseon how many exceptions found); 10. If DTS used,check for existence and functionality of packages; useDTSMigrationWizard.exe if packages non-existent at target, and if (aslikely) non-functional, determine whether to: - Replace failing non-upgradeable DTS package elements with their SSIS equivalents, or; - Encapsulate the package into an Execute DTS 2000 Package, or; - Create a new SSIS package from scratch 11. (Windows Team) re-point all users/groups to new server: What I'm not sure about yet: 1)Whether the target server(s) will be on the same domain(s) as thecurrent production boxes, and how this will affect the transfer oflogins/DTS; 2) Whether the network can handle a .bak file of 100Gb (last time I tried just 10Gb, the backup failed!) 3)Whether to use the Copy/Transfer database utilities (if same domain) orbackup/Attach (or is that Detach/Restore?!?!) with the consequentpossibilities of having to recreate logins/users/packages. 4) Handling cutover, as the size of the OLTP data will doubtless change if the systems are currently live. Any and all advice appreciated!! Jaybee.