On-prem MS SQL server 2016 migration to Azure SQL Server Managed database Instances path

Patankar, Narottam 20 Reputation points
2025-01-06T12:53:58.3333333+00:00

Hi Team,

We are currently planning to migrate our On-prem MS SQL Server 2016 to Azure SQL Server Managed Database Instances. The source will be our On-prem MS SQL Server 2016, and the target is the Azure SQL Server Managed Database Instances.

I have a few questions regarding this migration. Firstly, is it possible for us to migrate directly to MSSQL 2022, or do we need to first migrate to MSSQL 2019 before proceeding to 2022? Your insights on this would be greatly appreciated.

Additionally, it would be extremely helpful if you could provide us with a comprehensive SQL migration guide to ensure a smooth transition.

Thank you for your assistance and support.

Regards,

Narottam

Azure SQL Database
SQL Server Migration Assistant
SQL Server Migration Assistant
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
544 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Adharsh Santhanam 5,205 Reputation points
    2025-01-06T13:04:28.39+00:00

    Hello Patankar, Narottam, you can migrate directly from SQL 2016 to 2022 directly without needing to migrate to 2019. This direct migration is supported and can simplify your process. Here is a comprehensive migration guide that you'll find useful -- https://zcusa.951200.xyz/en-us/data-migration/sql-server/managed-instance/guide

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.


  2. Erland Sommarskog 115.3K Reputation points MVP
    2025-01-06T13:12:32+00:00

    You should be able to migrate without any intermediate versions.

    The one thing that you need to keep in mind is that always as when you migrate to a new version is that you can face backwards-compatibility issues. In practice, the biggest concern here is plan regressions, since there are changes in the optimizer.

    Once you have the database in Azure Managed Instance, make sure that Query Store is enabled. Keep the compatibility level on 130 (on whatever you have today). Run with this setting for a week or two. Then flip to level 160 to get benefit of the most recent enhancements. If some queries start to misbehave, you can use Query Store to force the old plans as a quick fix, while you make a more thorough analysis of the query. (When this happens it is often because there is some problem in the query or the indexing that you had some luck with avoiding the old compat level.)

    There is support in SSMS for these steps. Right-click the database in Object Explorer, select Tasks from the context menu. At the bottom, you find Database Upgrade.

    As for the migration, be sure to install the Azure Connect feature pack, which includes feature exactly to facilitate migration to Azure MI.


  3. Vijayalaxmi Kattimani 905 Reputation points Microsoft Vendor
    2025-01-07T09:55:25.9066667+00:00

    Hi @Patankar, Narottam,

    I would like to inform you that, the links mentioned below provide more information about migration. These links will help you prepare your environment to migrate from SQL Server to Azure SQL Managed Instance.

    https://zcusa.951200.xyz/en-us/data-migration/sql-server/managed-instance/guide

    https://zcusa.951200.xyz/en-us/data-migration/sql-server/pre-migration?tabs=sqlmi

    https://zcusa.951200.xyz/en-us/data-migration/sql-server/managed-instance/database-migration-service?tabs=online-with-extension

    Migration steps:

    To migrate your SQL Server to Azure SQL Managed Instance, follow these steps:

    • Review the SQL Server database engine features available in Azure SQL Managed Instance.
    • Choose a migration method and the corresponding tools for your method.
    • Create a performance baseline to determine resource usage on your source SQL Server instance. This step helps you deploy a properly sized managed instance so that performance after migration isn't affected.
    • Discover all SQL Server instances and features used by your organization.
    • Assess your SQL Server databases to identify migration blockers or compatibility issues.
    • Create a target SQL Managed Instance. Deploy an optimally sized managed instance where you choose technical characteristics (number of vCores, amount of memory) and performance tier (Business Critical, General Purpose) of your managed instance.
    • Configure connectivity and proper permissions to access both source and target.
    • Migrate your database where you migrate your databases using offline migration or online migration options.
    • Connect your application to Azure SQL Managed Instance.
    • Monitor and remediate applications to ensure that you see the expected performance.

    Screenshot of Steps for migration to Azure SQL Managed Instance.

    If the assessment encounters multiple blockers to confirm that your database isn't ready for an Azure SQL Managed Instance, then alternatively consider SQL Server on Azure Virtual Machines.

    I hope, This response will address your query and helped you to overcome on your challenges.

    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


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.