locked
Post Migration of databases from 2000 to R2 RRS feed

  • Question

  • Hi guys I have migrated several databases from 2000 server to R2. I have set the backup plans remapped the logins and everything looks fine. I have took the old databases offline. We have created the new DNS alias. What are the post migration issues that I should take care of once the databases are completely online?
    Sunday, June 26, 2011 5:57 PM

Answers

  • here are few

    1.Change the compatibility level of the databases (Optional)
    2.Do this if the applications connecting to these databases are independent of the database compatibility level.
    3.Transfer logins using SSIS (Transfer Logins Task) or using "sp_help_revlogin"
    4.More information about sp_help_revlogin is at http://support.microsoft.com/kb/246133
    5.Check for Orphaned Users in the databases and Fix them (if Any)
    6.Update Usage on the migrated Databases
    7.Update Stats on the migrated Databases
    8.Re-Index or Re-Organize Indexes on the migrated Databases
    9.Transfer Jobs using SSIS or manually create them
    10.Build Maintenance plans (if Any)
    11.Recompile database objects if required
    12.Move or rebuild SSIS or DTS packages (if Any)
    13.Create Alerts and Operators (if Any)
    14.Setup High Availability Options (if Any Like Replication, LogShipping, Mirroring)
    15.Test the High Availability options that were setup in the previous step
    16.Point the Application(s) to new Server and start the Application Service(s)
    17.Test the Application(s)

    more help here http://blogs.technet.com/b/mdegre/archive/2009/07/21/migration-sql-server-2000-to-sql-server-2008.aspx

     

     


    http://uk.linkedin.com/in/ramjaddu
    • Marked as answer by Sqldbar2 Monday, June 27, 2011 1:57 PM
    Monday, June 27, 2011 8:06 AM

All replies

  • here are few

    1.Change the compatibility level of the databases (Optional)
    2.Do this if the applications connecting to these databases are independent of the database compatibility level.
    3.Transfer logins using SSIS (Transfer Logins Task) or using "sp_help_revlogin"
    4.More information about sp_help_revlogin is at http://support.microsoft.com/kb/246133
    5.Check for Orphaned Users in the databases and Fix them (if Any)
    6.Update Usage on the migrated Databases
    7.Update Stats on the migrated Databases
    8.Re-Index or Re-Organize Indexes on the migrated Databases
    9.Transfer Jobs using SSIS or manually create them
    10.Build Maintenance plans (if Any)
    11.Recompile database objects if required
    12.Move or rebuild SSIS or DTS packages (if Any)
    13.Create Alerts and Operators (if Any)
    14.Setup High Availability Options (if Any Like Replication, LogShipping, Mirroring)
    15.Test the High Availability options that were setup in the previous step
    16.Point the Application(s) to new Server and start the Application Service(s)
    17.Test the Application(s)

    more help here http://blogs.technet.com/b/mdegre/archive/2009/07/21/migration-sql-server-2000-to-sql-server-2008.aspx

     

     


    http://uk.linkedin.com/in/ramjaddu
    • Marked as answer by Sqldbar2 Monday, June 27, 2011 1:57 PM
    Monday, June 27, 2011 8:06 AM
  • Thank you
    Monday, June 27, 2011 1:58 PM