locked
SQL Server 2008R2 Migration RRS feed

  • Question

  • I will be migrating over a SQL Server to 2008R2. I have the server built and the roles installed. I even have SQL2008R2 installed on it and have successfully moved over a test database. The biggest question involves the SSL certificate that is on the server. Please let me know of any holes that you see in my plan below.

    1. Detach all tables in the currently operating server

    2. Copy those tables over to the new server

    3. Attach the tables

    4. Bring down the old server

    5. Rename the new server to the same name as the old

    6. Change the IP address to the same as the old server

    7. Attach to the databases and verify their existence

    I believe that the certificate will also operate properly since the server is the same name and IP as the location where it is now working. I will even move the wire over so that it is the same switch and port as the old server. Since the specs are the same (other than 2008R2 SQL on 64 bit OS) all connection strings will continue to work. Any issues foreseen with this plan?

    Friday, October 5, 2012 11:47 AM

Answers

  • Hi Slink9,

    You are correct to rename the new server and the IP address as the old one after the old server is shutdown. And SSL certificate can work well with the same name and same IP address. Because once the server sends the certificate, the client examines it and compares the name it was trying to connect to with the name(s) included in the certificate. If a match is found the connection proceeds as normal.  If a match is not found, then the user may be warned of the discrepancy and the connection may be aborted as the mismatch.

    Please try to backup the database on the old server before you do the Migration. Then you can restore the database if it has any accident during the process.

    Please refer to:
    Server name Indication: http://en.wikipedia.org/wiki/Server_Name_Indication.
     
    Regards,
    Amy Peng


    Amy Peng

    TechNet Community Support



    • Edited by Amy Peng Monday, October 8, 2012 5:52 AM
    • Marked as answer by SLink9 Monday, October 8, 2012 5:31 PM
    Monday, October 8, 2012 1:49 AM

All replies

  • Hi Slink9,

    You are correct to rename the new server and the IP address as the old one after the old server is shutdown. And SSL certificate can work well with the same name and same IP address. Because once the server sends the certificate, the client examines it and compares the name it was trying to connect to with the name(s) included in the certificate. If a match is found the connection proceeds as normal.  If a match is not found, then the user may be warned of the discrepancy and the connection may be aborted as the mismatch.

    Please try to backup the database on the old server before you do the Migration. Then you can restore the database if it has any accident during the process.

    Please refer to:
    Server name Indication: http://en.wikipedia.org/wiki/Server_Name_Indication.
     
    Regards,
    Amy Peng


    Amy Peng

    TechNet Community Support



    • Edited by Amy Peng Monday, October 8, 2012 5:52 AM
    • Marked as answer by SLink9 Monday, October 8, 2012 5:31 PM
    Monday, October 8, 2012 1:49 AM
  • Why don't you try "In Place" Upgrade...

    Regards,

    Sandesh Segu

    http://www.SansSQL.com

    SansSQL

    ↑ Grab this Headline Animator

    Monday, October 8, 2012 3:49 PM
  • Reason for no In-Place upgrade is going from 32 bit to 64 bit OS and we need the least amount of downtime possible. I have the 64 bit machine built and updated and detach/attach is the easiest route to take, as far as I can tell.

    Amy, it sounds like I have a good plan. Thanks for the input and the link. I will check that out.

    Monday, October 8, 2012 5:31 PM