Tutorial: Migrate SQL Server to an Azure SQL Database managed instance offline using DMS
You can use the Azure Database Migration Service to migrate the databases from an on-premises SQL Server instance to an Azure SQL Database managed instance. For additional methods that may require some manual effort, see the article SQL Server instance migration to Azure SQL Database managed instance.
In this tutorial, you migrate the Adventureworks2012 database from an on-premises instance of SQL Server to an Azure SQL Database managed instance by using the Azure Database Migration Service.
In this tutorial, you learn how to:
- Create an instance of the Azure Database Migration Service.
- Create a migration project by using the Azure Database Migration Service.
- Run the migration.
- Monitor the migration.
- Download a migration report.
When you migrate databases to Azure by using Azure Database Migration Service, you can do an offline or an online migration. With an offline migration, application downtime starts when the migration starts. With an online migration, downtime is limited to the time to cut over at the end of migration. We suggest that you test an offline migration to determine whether the downtime is acceptable; if not, do an online migration.
This article describes an offline migration from SQL Server to an Azure SQL Database managed instance. For an online migration, see Migrate SQL Server to an Azure SQL Database managed instance online using DMS.
To complete this tutorial, you need to:
Create an Azure Virtual Network (VNet) for the Azure Database Migration Service by using the Azure Resource Manager deployment model, which provides site-to-site connectivity to your on-premises source servers by using either ExpressRoute or VPN. Learn network topologies for Azure SQL Database managed instance migrations using the Azure Database Migration Service. For more information about creating a VNet, see the Virtual Network Documentation, and especially the quickstart articles with step-by-step details.
During VNet setup, if you use ExpressRoute with network peering to Microsoft, add the following service endpoints to the subnet in which the service will be provisioned:
- Target database endpoint (for example, SQL endpoint, Cosmos DB endpoint, and so on)
- Storage endpoint
- Service bus endpoint
This configuration is necessary because the Azure Database Migration Service lacks internet connectivity.
Ensure that your VNet Network Security Group rules don't block the following inbound communication ports to Azure Database Migration Service: 443, 53, 9354, 445, 12000. For more detail on Azure VNet NSG traffic filtering, see the article Filter network traffic with network security groups.
Configure your Windows Firewall for source database engine access.
Open your Windows Firewall to allow the Azure Database Migration Service to access the source SQL Server, which by default is TCP port 1433.
If you're running multiple named SQL Server instances using dynamic ports, you may wish to enable the SQL Browser Service and allow access to UDP port 1434 through your firewalls so that the Azure Database Migration Service can connect to a named instance on your source server.
If you're using a firewall appliance in front of your source databases, you may need to add firewall rules to allow the Azure Database Migration Service to access the source database(s) for migration, as well as files via SMB port 445.
Create an Azure SQL Database managed instance by following the detail in the article Create an Azure SQL Database managed instance in the Azure portal.
Ensure that the logins used to connect the source SQL Server and target managed instance are members of the sysadmin server role.
Create a network share that the Azure Database Migration Service can use to back up the source database.
Ensure that the service account running the source SQL Server instance has write privileges on the network share that you created and that the computer account for the source server has read/write access to the same share.
Make a note of a Windows user (and password) that has full control privilege on the network share that you previously created. The Azure Database Migration Service impersonates the user credential to upload the backup files to Azure storage container for restore operation.
Create a blob container and retrieve its SAS URI by using the steps in the article Manage Azure Blob Storage resources with Storage Explorer, be sure to select all permissions (Read, Write, Delete, List) on the policy window while creating the SAS URI. This detail provides the Azure Database Migration Service with access to your storage account container for uploading the backup files used for migrating databases to Azure SQL Database managed instance.
Register the Microsoft.DataMigration resource provider
Sign in to the Azure portal, select All services, and then select Subscriptions.
Select the subscription in which you want to create the instance of the Azure Database Migration Service, and then select Resource providers.
Search for migration, and then to the right of Microsoft.DataMigration, select Register.
Create an Azure Database Migration Service instance
In the Azure portal, select + Create a resource, search for Azure Database Migration Service, and then select Azure Database Migration Service from the drop-down list.
On the Azure Database Migration Service screen, select Create.
On the Create Migration Service screen, specify a name for the service, the subscription, and a new or existing resource group.
Select the location in which you want to create the instance of DMS.
Select an existing VNet or create one.
The VNet provides the Azure Database Migration Service with access to the source SQL Server and target Azure SQL Database managed instance.
For more information on how to create a VNet in Azure portal, see the article Create a virtual network using the Azure portal.
For additional detail, see the article Network topologies for Azure SQL DB managed instance migrations using the Azure Database Migration Service.
Select a pricing tier.
For more information on costs and pricing tiers, see the pricing page.
Select Create to create the service.
Create a migration project
After an instance of the service is created, locate it within the Azure portal, open it, and then create a new migration project.
In the Azure portal, select All services, search for Azure Database Migration Service, and then select Azure Database Migration Services.
On the Azure Database Migration Service screen, search for the name of the instance that you created, and then select the instance.
Select + New Migration Project.
On the New migration project screen, specify a name for the project, in the Source server type text box, select SQL Server, in the Target server type text box, select Azure SQL Database Managed Instance, and then for Choose type of activity, select Offline data migration.
Select Create to create the project.
Specify source details
On the Migration source detail screen, specify the connection details for the source SQL Server.
If you haven't installed a trusted certificate on your server, select the Trust server certificate check box.
When a trusted certificate isn't installed, SQL Server generates a self-signed certificate when the instance is started. This certificate is used to encrypt the credentials for client connections.
SSL connections that are encrypted using a self-signed certificate does not provide strong security. They are susceptible to man-in-the-middle attacks. You should not rely on SSL using self-signed certificates in a production environment or on servers that are connected to the internet.
On the Select source databases screen, select the Adventureworks2012 database for migration.
If you use SQL Server Integration Services (SSIS), DMS does not currently support migrating the catalog database for your SSIS projects/packages (SSISDB) from SQL Server to Azure SQL Database managed instance. However, you can provision SSIS in Azure Data Factory (ADF) and redeploy your SSIS projects/packages to the destination SSISDB hosted by Azure SQL Database managed instance. For more information about migrating SSIS packages, see the article Migrate SQL Server Integration Services packages to Azure.
Specify target details
On the Migration target details screen, specify the connection details for the target, which is the pre-provisioned Azure SQL Database managed instance to which you're migrating the AdventureWorks2012 database.
If you haven't already provisioned the Azure SQL Database managed instance, select the link to help you provision the instance. You can still continue with project creation and then, when the Azure SQL Database managed instance is ready, return to this specific project to execute the migration.
Select source databases
On the Select source databases screen, select the source database that you want to migrate.
On the Select logins screen, select the logins that you want to migrate.
This release only supports migrating the SQL logins.
Configure migration settings
On the Configure migration settings screen, provide the following detail:
Choose source backup option Choose the option I will provide latest backup files when you already have full backup files available for DMS to use for database migration. Choose the option I will let Azure Database Migration Service create backup files when you want DMS to take the source database full backup at first and use it for migration. Network location share The local SMB network share that the Azure Database Migration Service can take the source database backups to. The service account running source SQL Server instance must have write privileges on this network share. Provide an FQDN or IP addresses of the server in the network share, for example, '\\servername.domainname.com\backupfolder' or '\\IP address\backupfolder'. User name Make sure that the Windows user has full control privilege on the network share that you provided above. The Azure Database Migration Service will impersonate the user credential to upload the backup files to Azure storage container for restore operation. If TDE-enabled databases are selected for migration, the above windows user must be the built-in administrator account and User Account Control must be disabled for Azure Database Migration Service to upload and delete the certificates files.) Password Password for the user. Storage account settings The SAS URI that provides the Azure Database Migration Service with access to your storage account container to which the service uploads the back-up files and that is used for migrating databases to Azure SQL Database managed instance. Learn how to get the SAS URI for blob container. TDE Settings If you're migrating the source databases with Transparent Data Encryption (TDE) enabled, you need to have write privileges on the target Azure SQL Database managed instance. Select the subscription in which the Azure SQL Database managed instance provisioned from the drop-down menu. Select the target Azure SQL Database Managed Instance in the drop-down menu.
Review the migration summary
On the Migration summary screen, in the Activity name text box, specify a name for the migration activity.
Expand the Validation option section to display the Choose validation option screen, specify whether to validate the migrated database for query correctness, and then select Save.
Review and verify the details associated with the migration project.
Run the migration
Select Run migration.
The migration activity window appears, and the status of the activity is Pending.
Monitor the migration
In the migration activity screen, select Refresh to update the display.
You can further expand the databases and logins categories to monitor the migration status of the respective server objects.
After the migration completes, select Download report to get a report listing the details associated with the migration process.
Verify that the target database on the target Azure SQL Database managed instance environment.
- For a tutorial showing you how to migrate a database to a managed instance using the T-SQL RESTORE command, see Restore a backup to a managed instance using the restore command.
- For information about managed instance, see What is a managed instance.
- For information about connecting apps to a managed instance, see Connect applications.