CHECKLIST FOR SQL SERVER MIGRATION

Below is the checlist for Server Migration . We migrated a from HP server to Dell Server So this was the process we followed.
-------------------------------------------

** CHECKLIST  FOR  SERVER  MIGRATION **
-------------------------------------------
1. Check the SQL Server Edition on "Source" and "Destination" machine.
2. Check the service pack on "Source" and "Destination" machine.
3. Document the existing SQL Server settings so that it should match the same (collation,version,...)
4. Take Full backups of all System and Application databases on "Source" machine.
5. Script all logins on "Source" and "Destination" machine.
6. Script all jobs on "Source" and "Destination" machine.
7. List out all Maintenance Plans and their schedules.
8. List out all Linked server(s) currently being used.

---------------------
Migration Process :
---------------------
1. Migrate logins (Please use the script - http://support.microsoft.com/kb/246133 to transfer the logins to the newly built server. In this way you dont have to fix any orphaned users)
2. Restore all Application Databases
3. Fix the Orphan Users, if required.
4. Create the jobs on the destination server, which you have scripted before starting the migration activity.
5. Create maintenance plans on the destination server.
6. Create Linked Servers on the destination server.
7. Perform checkdb on all databases.
8. Rebuild indexes on all databases.
9. Update the statistics on all databases.
10. Move all the DTS packages.
11. Point the application to new server
12. Testing ....

---------------------
NOTES:
---------------------
1. After you rename the physical server and startup the sql server, if run @@SERVERNAME u would find still the old server name getting reflected. You woud need to run the sp_dropserver and the sp_addserver to reflect the new name.
A simpler way would be once ur old machine is down, just restore the backup of the master db of the old machine. This way u avoid scripting logins, server level settings, linked servers etc. but a word of caution, the location of ur db files (msdb and other user db's) should be identical else sql server would refuse to startup.

2. Check the connectivity through the client tool (sql server EM or Query Analyzer) from another machine or a client machine. If there are connectivity probs u would need to troubleshoot further.

3. A good prac would be to keep ur mdf, ldf and tempdb files in different physical drives to isolate disk/IO. Also choose the approriate raid levels for the storage subsystem. Put a cap on max memory. Set a intial size for the temp db and create 2 temp data files to take adv of parallel processing of CPU. Set a intial size to all user db's and an auto grow option in either % or MB's.
4. Keep tempdb in diff physical disk with raid 10 preferrably.

------------------------------------------