• side by side migration, or an in place upgrade?

    there's not a lot of difference in the preperation, as compared to a full on disaster recovery plan....if the new server doesn't come up, or the existing server goes kaput, it's the same thing;

    my quickie checklist i have saved:

    - Back up all databases(tail, without recovery)

    - Export logins/hashed passwords using sp_help_revlogin

    - Export any certificates/master keys/database keys

    - Export linked servers

    - Export Mail settings from msdb

    Export jobs from msdb

    - Reload

    - Install SQL 2008 R2, and leave it unpatched

    - Restore jobs script after find/replace(to get our maintenance plans back)

    - Restore the user databases

    - Import the logins/usernames and verify mapping

    - Patch SQL up to current

    few other things you may want to script out or keep track of if they apply:

    • sp_configure

    • Alerts

    • Operators

    • Jobs

    • SQL Agent config

    • Database Mail config

    • Trace Flags DBCC TRACESTATUS

    • Linked Servers

    • Replication publications or subscriptions

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!