Migration to Azure SQL Managed Instance - SQL Server migration in Azure Arc

Applies to: SQL Server

This article shows you how to perform a SQL Server migration in Azure Arc to Azure SQL Managed Instance in the Azure portal for your SQL Server instance enabled by Azure Arc.

You can try Azure SQL Managed Instance for free for up to a year.

Note

You can provide feedback on your migration experience directly to the product group.

Overview

Azure SQL Managed Instance is a fully managed lift-and-shift platform as a service (PaaS) target to run your SQL Server workloads on the Azure cloud platform. After your SQL Server instance is enabled by Azure Arc, you can assess your SQL Server data estate to identify an optimal SQL Managed Instance configuration. Then you can migrate your SQL Server databases to SQL Managed Instance directly from the Azure portal.

When your SQL Server instance is enabled by Azure Arc, you can:

• Evaluate and assess whether your SQL Server instance is ready to migrate to SQL Managed Instance.
• Identify potential migration issues, and learn how to mitigate them.
• Optimize for performance and cost with guidance around service tiers, configuration, and sizing.

Discovery of SQL Server instances and generation of readiness reports happen automatically every weekend, but you can start them manually at any time. The process takes only a few minutes to complete. No extra configuration or setup is required.

First, you choose an appropriate SQL Managed Instance target and prepare your environment. Then, you can migrate your SQL Server databases to SQL Managed Instance directly from the Azure portal through a fully managed and automated process.

Database migration is available by default for all SQL Server instances enabled by Azure Arc, starting with SQL Server 2012 (11.x).

The Database Migration pane also has a useful summary of the migration status for your instance, such as the number of total databases, the recommended target, the number of completed migrations, and the number of ongoing migrations:

Integrated migration methods

Choose the migration method that best fits your needs on the Database migration pane. After an initial configuration to prepare your environment, the migration process automates the rest based on your selection.

Microsoft Copilot can help you choose the right migration method based on your requirements.

The following table summarizes the two methods built into the migration process:

	Managed Instance link	Log Replay Service (LRS)
Method	Real time replication	Continuous backup and restore
Underlying technology	Distributed availability group	Log shipping
Description	Most performant method with near real-time replication. Provides a read-only (R/O) database on the target, so you can query your data in near-real time during the migration to offload R/O workloads on the secondary, or check data during the migration. Best possible minimum downtime migration.	Most compatible migration method. Upload backups to an intermediary Azure blob storage account that the LRS service automatically restores to SQL Managed Instance continuously. No R/O database replica is available on the target.
Supported versions	SQL Server 2016 and later on Windows Server 2016 and later	SQL Server 2012 and later on Windows Server 2012 and later
Supported editions	Enterprise, Standard, and Developer editions	All editions
Recommended for	Business-critical workloads that require minimum downtime during migration and access to a read-only database on the target, with a destination target of either a General Purpose or Business Critical SQL Managed Instance.	General purpose workloads where some planned downtime is acceptable and destination target of a General Purpose SQL Managed Instance. Not recommended for Business Critical SQL managed instance targets.

For an in-depth comparison of the two migration methods, see Compare Managed Instance link with LRS for migration.

Microsoft Copilot assisted migration

Microsoft Copilot is built into the experience to assist you throughout the migration process. Interactively chatting with Microsoft Copilot searches through the Microsoft knowledgebase to help you along the way as you migrate to Azure.

Microsoft Copilot provides AI-powered assistance to help you make decisions or take actions at certain points with prompts such as:

• How are assessments made?
• Help me compare.
• Start the migration.
• Help me choose the right migration method.
• Monitor the migration.
• Complete the migration.

Select the Copilot icon on the Database migration pane to open the Copilot chat window:

Prerequisites

To use SQL Server migration in Azure Arc, you need the following prerequisites:

• An active Azure subscription. If you don't have one, you can create a free account.
• Your SQL Server instance must be enabled by Azure Arc with the Azure extension for SQL Server version 1.1.3211.337 or later. You can upgrade your extension by using the Azure portal or the Azure CLI.

Before you start the migration process, make sure that you've prepared your environment for your chosen migration method:

• Prepare for Managed Instance link migration.
• Prepare for LRS migration.

Migrate to Azure SQL Managed Instance

The following tiles on the Database Migration pane guide you through the migration of your SQL Server databases to Azure SQL Managed Instance:

1. Assess source instance: Assess your SQL Server instance to determine its readiness to migrate to SQL Managed Instance.
2. Select target: Select a SQL Managed Instance target for your migration.
3. Migrate data: Migrate your SQL Server databases to SQL Managed Instance.
4. Monitor and cutover: Monitor the migration process and cut over to the SQL Managed Instance target.

The following screenshot shows the tiles on the Database migration pane for your SQL Server instance in the Azure portal:

Assess source instance

To assess the source instance, follow these steps:

1. Go to your SQL Server instance in the Azure portal.

2. Under Migration, select Database migration to open the Database migration pane. Under Assess source instance, select View report to open the Assessments pane.

   

3. On the Assessments pane:

   • Use Run assessment to start a new assessment if one wasn't run recently.
   • Use View assessment details in the Azure SQL MI Recommended Target box to learn more about your assessment results, including the readiness of your SQL Server instance to migrate to SQL Managed Instance. You also learn about the recommended service tier and configuration for your target instance.

Select target

After you assess your SQL Server instance, select a SQL Managed Instance target.

1. On the Assessments pane, select Create or select target. Or, on the Database migration pane, select Select target. Both options open the Create or select target pane where you can identify a migration target.

   

2. On the Create or select target pane, under Target exists, select one of the following options:

   • Yes, I have already created a target: Select an existing SQL Managed Instance target.
   • No, I want to create a new target: Create a new SQL Managed Instance target.

   

3. Fill in the required information for the SQL Managed Instance target. Then use either Select target or Create target to proceed to the next step based on your Target exists selection.

   1. If you already have an instance as a target, choosing Select target takes you to the Database migration pane for your SQL Server instance. The instance name is populated as the selected target. Then you can proceed to the Migrate data step.
   2. If you chose to create a new instance, you're guided to the Create Azure SQL Managed Instance pane on the Database migration pane to create the target instance. After you finish, check the progress of the deployment on the Database migration pane for your SQL Server instance. The target name populates in the Target tile. Then you can proceed to the Migrate data step.

Migrate data

After your target is ready, start the migration process.

MI link migration

Once you've prepared your environment for Managed Instance link migration, you can migrate your SQL Server databases to Azure SQL Managed Instance.

Follow these steps to migrate your SQL Server databases to SQL Managed Instance by using the Managed Instance link:

1. On the Database migration pane, select Migrate data.

2. On the New data migration pane, choose Migrate using real-time replication (online):

   

3. On the Select source databases tab, check the boxes next to the databases that you want to migrate, and then use Next: Settings to proceed to the next page:

   

4. On the Settings tab, provide the name of the MI link. The name of the availability group is autogenerated - customize it, only if you need to. You can also use Test connection to test the connection to the source SQL Server instance, though be aware that false positives can occur in some network configurations. Use Next: Review + create to proceed to the next page:

   

   You can also test the connection to the target SQL Managed Instance

5. On the Review + create tab, review the settings, and check for warnings. It's possible to start the migration with some warnings, but not others. Select Start data migration to migrate your data to your SQL Managed Instance target.

Note

When you start the migration process by using the Managed Instance link migration method, the system grants just-in-time permissions for the entire workflow until creating the distributed availability group completes, at which point just-in-time permissions are removed.

LRS migration

Once you've prepared your environment for LRS migration, you can migrate your SQL Server databases to Azure SQL Managed Instance.

Selections on the New data migration page aren't available, or will error out, after you choose LRS unless the Azure Blob Storage account has at least one single full backup, and permissions are correctly set.

LRS migration relies on backups that you upload to an intermediary Azure Blob Storage account. If you have multiple backups, or want to have a continuous migration, you need to continue uploading backups to the same blob storage account until you're ready to cut over.

Follow these steps to migrate your SQL Server databases to SQL Managed Instance by using LRS:

1. On the Database migration pane, select Migrate data.

2. On the New data migration pane, choose Migrate using log shipping (online), and then use Select to proceed to the next page:

   

3. On the Select source databases tab, check the boxes next to the databases that you want to migrate, and then use Next to proceed to the next page:

   

4. On the Azure Blob Storage details tab, provide the subscription, location, resource group, blob container, and directory details for where you stored your backups.

5. On the Review + create tab, review the settings, and check for errors and warnings. While it's possible to start the migration when there are warnings, the warnings should be addressed at some point to ensure a successful long-term migration. Select Start data migration to migrate your data to your SQL Managed Instance target.

Monitor and cutover

After you start your migration, you can monitor the progress. On the Database migration pane, select Monitor migrations.

The Monitor and cutover pane shows useful information about the migration process, such as:

• The databases that successfully migrated and the databases that are still in progress.
• The chosen migration method.
• The target instance and target database.
• The duration of the current migration of each database.
• The time when the migration started.

You can complete or cancel the migration from the Monitor and cutover pane. You can also view logs for information about the migration. Selecting a database takes you to a pane with more details about the source and target.

After the migration finishes, the migration status shows Ready for cutover. To cut over to the SQL Managed Instance target, select Cutover on the Monitor and cutover pane. You can also use the database details pane.

Select a database and then use Cutover to open the Cutover pane and see different options based on the migration method that you selected.

Note

Completing the cutover or canceling the migration when you migrate with the Managed Instance link grants just-in-time permissions until the link is removed or the migration is canceled.

Limitations

The limitations of the Managed Instance link and LRS apply to migrations through the Azure portal.

Monitoring the migration through the Azure portal is available only to SQL Server instances that meet monitoring licensing requirements.

Related content

• Assessment rules for SQL Server to Azure SQL Managed Instance migration
• Assessment rules for SQL Server to Azure SQL Database migration
• Migrate SQL Server to Azure SQL
• SQL Server enabled by Azure Arc
• Deployment options for SQL Server enabled by Azure Arc
• Migration experience feedback directly to the product group