Migration of SQL Server 2016 to new Windows Server 2019 Standard Machine

ahmed qureshi 21 Reputation points
2020-10-20T12:02:51.88+00:00

Hi,

We are planning to migrate all of our Windows Server 2012 R2 Standard to Server 2019 Standard. For this, we will have to migrate our SQL server 2016 (2 instances Running in windows cluster) to new Windows Server 2019 Standard server machines. We have got the VMware virtualized environment and these SQL server are serving as a single central point for all application's databases running in environment such as Sharepoint, ManageEngine reporting tools etc.

Can any one please guide us through the detailed step by step process to migrate our SQL server instances to new Server 2019 with healthier and smooth transition without loosing any data or application.

Also, do we need license key if we upgrade from SQl server 2016 to 2019 during this OS migration?

Thanks and Regards
Ali,

SQL Server Other
{count} votes

6 answers

Sort by: Most helpful
  1. Leon Laude 86,026 Reputation points
    2020-10-20T12:38:05.503+00:00

    Hi @ahmed qureshi ,

    You can follow the official Microsoft documentations mentioned in the links below.
    If you migrate your SQL Server to another server, you will need the license key for the new SQL Server yes, you can have a look at the Data Migration Assistant tool below:

    Upgrade SQL Server
    https://learn.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server?view=sql-server-ver15

    SQL Server migration documentation
    https://learn.microsoft.com/en-us/sql/sql-server/migrate/?view=sql-server-ver15

    Upgrade SQL Server using the Data Migration Assistant
    https://learn.microsoft.com/en-us/sql/dma/dma-migrateonpremsql?view=sql-server-ver15

    ----------

    (If the reply was helpful please don't forget to upvote or accept as answer, thank you)

    Best regards,
    Leon


  2. Shashank Singh 6,251 Reputation points
    2020-10-20T12:40:13.337+00:00

    The best way I think of is

    1. Transaction Logshipping
    2. Mirroring
    3. Replication

    What you need to do is

    1. Build a new system with new Server 2019 OS.
    2. Install SQL Server 2016 on it.
    3. Backup user and system databases on old system and move it to new system
    4. Restore master and msdb database back. This will create all logins, jobs and other system objects
    5. Configure mirroring, logshipping etc whatever suits you to migrate database, for all the database
    6. On the day of cutover stop application, put databases in read_only mode ( if possible) , and bring DB online on destination system.
    7. Connect application to new system. You might need to change the connection string.
    8. If you do not want to change connection string keep instance name of SQL Server same on default machine. Post cutover rename original system to Winserver_old . Now the name is free use this and rename new system with the old name.
    9. Wait for 10 mins for propagation and then you are good to go.
    10. Post changing hostname use TSQL to make sure changes is reflected in SQL Server.

    EDIT: Missed below question

    do we need license key if we upgrade from SQl server 2016 to 2019 during this OS migration?

    Since you are keeping SQL Server version same and just moving to new OS you do not need new SQL Server version. You would need license for Win server 2019 though


  3. AmeliaGu-MSFT 14,006 Reputation points Microsoft External Staff
    2020-10-21T02:52:32.47+00:00

    Hi @ahmed qureshi ,

    You can use DMA (Data Migration Assistant) to migrate SQL Server. DMA will recommend performance and reliability improvements for your target environment and allows you to move your schema, data, and uncontained objects from your source server to your target server.
    Before using DMA to migrate SQL Server, you can use MAP (Microsoft Assessment and Planning tool) to do an audit of your landscape, database and so on.
    After migrating SQL Server, you can use DEA (Database Experimentation Assistant) to assist with evaluating the target SQL Server.
    For more details, please refer to tutorials which might help:
    SQL Server upgrades
    Upgrade SQL Server to SQL Server

    In addition, for detailed information about the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the https://www.microsoft.com/en-us/licensing/worldwide to find contact information in your locations. For Volume Licensing Service Support, please use the https://learn.microsoft.com/en-us/licensing/contact-us to contact information for your country.

    Best Regards,
    Amelia


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  4. ahmed qureshi 21 Reputation points
    2020-11-05T07:10:11.523+00:00

    Hi All,

    Thanks for your precious response. We have not yet started the migration process. Lets give us some time so we can plan and start the process to verify the steps to see if it helps.

    Thanks

    0 comments No comments

  5. ahmed qureshi 21 Reputation points
    2020-11-23T12:43:25.507+00:00

    Hi All,

    Actually we have 2 SQL server 2016 nodes running under windows clustering service. We are planning to migrate both windows OS and the SQL server to 2019 servers.

    This SQL instance is holding the Databases for our Sharepoint application. We will be using DMA approach for this migration. But before that we need to know that do we need to make new that SQl server 2019 machine part of existing windows cluster which is on server 2012 R2? or we can simply migrate the databases (using DMA) from older SQl server to new SQl server machine without making is part of cluster?

    Please help

    Thanks

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.