Server Migration

  • You may need to update any aliases your servers or clients could be using:

    cliconfg.exe

  • We are also doing a Physical migration from one data center to another which we call " Lift and Shift".

    As others mentioned

    1. Application connection string changes in config files

    2. Take backups and test them

    I would add ...

    1. Code freeze ... no new build or code should be deployed

    2. when the servers are back online .. run DBCC check DB to ensure everything is fine and clean.

    3. reconfigure backups according to new path

    Hope this helps,

    \\K

    ______________________________________________________________________________________________________________________________________________________________________________________
    HTH !
    Kin
    MCTS : 2005, 2008
    Active SQL Server Community Contributor 🙂

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply