March 5, 2015 at 1:02 pm
Hi
I have been looking around for Migration Checklist and the below is the procedure suits ideal for environment.
Pre-Migration CheckList:
Assuming the applications supports the SQL Version which we are migrating it to.
1. Check/update the Stats on tables.
2. DBCC CheckDB on all the databases to find any corrupt pages.
3. Cleanse the server by removing unwanted jobs, Logins,.....
4. Higher level info collect the statistical information of SQL Server Configurations, Database size, Disk/Drive Size, Database growth size for a period of time(historical).
5. Once you are done the above ensure the new environment has enough Storage Space the databases, Backups, Configurations,...
6. Run the Upgrade advisor and see if any deprecated features exists in current environment and then work on it to upgrade/replace them.
7. Now that you have checked all 1-6 above you will have an idea of how much time does it takes for a Backup/Restore of the Databases, moving the logins, jobs, packages,alerts, operators,..... Plan the downtime for migration. It would be easy for an environment with few databases and low sizes; considering the numerous databases and huge sizes set up log shipping or mirroring prior migration.
Migration:
Since you have planned downtime
1. Run the scripts to do the Backup on old server and Restores on new servers.
2. Run the scripts to configure jobs, logins, alerts, operators,...
2. For the environments with large number of databases and huge in sizes run the script to take the tail log back up and restore them on the new destinations with recovery.
Post Migration:
1. Ensure the database sizes.
2. Ensure all the jobs, logins, alerts, operators, maintenance plans,...
3. Change the compatibility, owners as needed for the databases
4. Fix the orphan users in the databases.
5. point the users to the databases and validate if they could access and say things are fine.
I used this procedure and It worked out please add steps If I missed any important ones. Anyone with Migration of similar environment can read this a summary and dig deeper to work it out. Also please ensure with your environment before taking any steps. Good Luck Migration Guys.:-)
March 6, 2015 at 11:37 am
Before you move run this special version of CHECKDB on each database
DBCC CHECKDB with data_purity
If you have time it is a good idea when you upgrade to a new version of SQL Server to rebuild all indexes so that the optimizer can use its new stats algorithim for access paths. If you do not have enough time to rebuild indexes on large database at minimum run an update stats on those databases.
March 6, 2015 at 2:02 pm
udaynov17 (3/5/2015)
HiI have been looking around for Migration Checklist and the below is the procedure suits ideal for environment.
Pre-Migration CheckList:
Assuming the applications supports the SQL Version which we are migrating it to.
1. Check/update the Stats on tables.
2. DBCC CheckDB on all the databases to find any corrupt pages.
3. Cleanse the server by removing unwanted jobs, Logins,.....
4. Higher level info collect the statistical information of SQL Server Configurations, Database size, Disk/Drive Size, Database growth size for a period of time(historical).
5. Once you are done the above ensure the new environment has enough Storage Space the databases, Backups, Configurations,...
6. Run the Upgrade advisor and see if any deprecated features exists in current environment and then work on it to upgrade/replace them.
7. Now that you have checked all 1-6 above you will have an idea of how much time does it takes for a Backup/Restore of the Databases, moving the logins, jobs, packages,alerts, operators,..... Plan the downtime for migration. It would be easy for an environment with few databases and low sizes; considering the numerous databases and huge sizes set up log shipping or mirroring prior migration.
Migration:
Since you have planned downtime
1. Run the scripts to do the Backup on old server and Restores on new servers.
2. Run the scripts to configure jobs, logins, alerts, operators,...
2. For the environments with large number of databases and huge in sizes run the script to take the tail log back up and restore them on the new destinations with recovery.
Post Migration:
1. Ensure the database sizes.
2. Ensure all the jobs, logins, alerts, operators, maintenance plans,...
3. Change the compatibility, owners as needed for the databases
4. Fix the orphan users in the databases.
5. point the users to the databases and validate if they could access and say things are fine.
I used this procedure and It worked out please add steps If I missed any important ones. Anyone with Migration of similar environment can read this a summary and dig deeper to work it out. Also please ensure with your environment before taking any steps. Good Luck Migration Guys.:-)
You can include running SQL Server Upgrade Advisor
March 9, 2015 at 7:48 am
I included in the 6th step pre-migration check list.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply