Tutorial: Migrate SQL Server to SQL Server on Azure Virtual Machine online using Azure Data Studio with DMS

Use the Azure SQL migration extension in Azure Data Studio to migrate the databases from a SQL Server instance to a SQL Server on Azure Virtual Machine (SQL Server 2016 and above) with minimal downtime. For methods that may require some manual effort, see the article SQL Server instance migration to SQL Server on Azure Virtual Machine.

In this tutorial, you migrate the AdventureWorks database from an on-premises instance of SQL Server to a SQL Server on Azure Virtual Machine with minimal downtime by using Azure Data Studio with Azure Database Migration Service.

In this tutorial, you learn how to:

  • Launch the Migrate to Azure SQL wizard in Azure Data Studio.
  • Run an assessment of your source SQL Server database(s)
  • Collect performance data from your source SQL Server
  • Get a recommendation of the SQL Server on Azure Virtual Machine SKU best suited for your workload
  • Specify details of your source SQL Server, backup location and your target SQL Server on Azure Virtual Machine
  • Create a new Azure Database Migration Service and install the self-hosted integration runtime to access source server and backups.
  • Start and monitor the progress for your migration.
  • Perform the migration cutover when you are ready.

This article describes an online migration from SQL Server to a SQL Server on Azure Virtual Machine. Offline migration, see Migrate SQL Server to a SQL Server on Azure Virtual Machine offline using Azure Data Studio with DMS.

Prerequisites

To complete this tutorial, you need to:

  • Download and install Azure Data Studio

  • Install the Azure SQL migration extension from the Azure Data Studio marketplace

  • Have an Azure account that is assigned to one of the built-in roles listed below:

    • Contributor for the target SQL Server on Azure Virtual Machine (and Storage Account to upload your database backup files from SMB network share).
    • Reader role for the Azure Resource Groups containing the target SQL Server on Azure Virtual Machine or the Azure storage account.
    • Owner or Contributor role for the Azure subscription.
    • As an alternative to using the above built-in roles you can assign a custom role as defined in this article.

    Important

    Azure account is only required when configuring the migration steps and is not required for assessment or Azure recommendation steps in the migration wizard.

  • Create a target SQL Server on Azure Virtual Machine.

    Important

    If you have an existing Azure Virtual Machine, it should be registered with SQL IaaS Agent extension in Full management mode.

  • Ensure that the logins used to connect the source SQL Server are members of the sysadmin server role or have CONTROL SERVER permission.

  • Use one of the following storage options for the full database and transaction log backup files:

    • SMB network share
    • Azure storage account file share or blob container

    Important

    • If your database backup files are provided in an SMB network share, Create an Azure storage account that allows the DMS service to upload the database backup files. Make sure to create the Azure Storage Account in the same region as the Azure Database Migration Service instance is created.
    • Azure Database Migration Service does not initiate any backups, and instead uses existing backups, which you may already have as part of your disaster recovery plan, for the migration.
    • Each backup can be written to either a separate backup file or multiple backup files. However, appending multiple backups (i.e. full and t-log) into a single backup media is not supported.
    • Use compressed backups to reduce the likelihood of experiencing potential issues associated with migrating large backups.
  • Ensure that the service account running the source SQL Server instance has read and write permissions on the SMB network share that contains database backup files.

  • The source SQL Server instance certificate from a database protected by Transparent Data Encryption (TDE) needs to be migrated to the target SQL Server on Azure Virtual Machine before migrating data. To learn more, see Move a TDE Protected Database to Another SQL Server.

    Tip

    If your database contains sensitive data that is protected by Always Encrypted, migration process using Azure Data Studio with DMS will automatically migrate your Always Encrypted keys to your target SQL Server on Azure Virtual Machine.

  • If your database backups are in a network file share, provide a machine to install self-hosted integration runtime to access and migrate database backups. The migration wizard provides the download link and authentication keys to download and install your self-hosted integration runtime. In preparation for the migration, ensure that the machine where you plan to install the self-hosted integration runtime has the following outbound firewall rules and domain names enabled:

    Domain names Outbound ports Description
    Public Cloud: {datafactory}.{region}.datafactory.azure.net
    or *.frontend.clouddatahub.net
    Azure Government: {datafactory}.{region}.datafactory.azure.us
    China: {datafactory}.{region}.datafactory.azure.cn
    443 Required by the self-hosted integration runtime to connect to the Data Migration service.
    For new created Data Factory in public cloud, locate the FQDN from your Self-hosted Integration Runtime key, which is in format {datafactory}.{region}.datafactory.azure.net. For old Data factory, if you don't see the FQDN in your Self-hosted Integration key, use *.frontend.clouddatahub.net instead.
    download.microsoft.com 443 Required by the self-hosted integration runtime for downloading the updates. If you have disabled auto-update, you can skip configuring this domain.
    *.core.windows.net 443 Used by the self-hosted integration runtime that connects to the Azure storage account for uploading database backups from your network share

    Tip

    If your database backup files are already provided in an Azure storage account, self-hosted integration runtime is not required during the migration process.

  • Runtime is installed on the machine using self-hosted integration runtime. The machine will connect to the source SQL Server instance and the network file share where backup files are located. Outbound port 445 should be enabled to allow access to the network file share. Also see recommendations for using self-hosted integration runtime

  • If you're using the Azure Database Migration Service for the first time, ensure that Microsoft.DataMigration resource provider is registered in your subscription. You can follow the steps to register the resource provider

Launch the Migrate to Azure SQL wizard in Azure Data Studio

  1. Open Azure Data Studio and select on the server icon to connect to your on-premises SQL Server (or SQL Server on Azure Virtual Machine).
  2. On the server connection, right-click and select Manage.
  3. On the server's home page, Select Azure SQL Migration extension.
  4. On the Azure SQL Migration dashboard, select Migrate to Azure SQL to launch the migration wizard. Launch Migrate to Azure SQL wizard
  5. In the first step of the migration wizard, link your existing or new Azure account to Azure Data Studio.

Run database assessment, collect performance data and get Azure recommendation

  1. Select the database(s) to run assessment and select Next.
  2. Select SQL Server on Azure Virtual Machine as the target. Assessment confirmation
  3. Select on the View/Select button to view details of the assessment results for your database(s), select the database(s) to migrate, and select OK.
  4. Click the Get Azure recommendation button.
  5. Pick the Collect performance data now option and enter a path for performance logs to be collected and click the Start button.
  6. Azure Data Studio will now collect performance data until you either stop the collection, press the Next button in the wizard or close Azure Data Studio.
  7. After 10 minutes you will see a recommended configuration for your Azure SQL VM. You can also press the Refresh recommendation link after the initial 10 minutes to refresh the recommendation with the additional data collected.
  8. In the above SQL Server on Azure Virtual Machine box click the View details button for more information about your recommendation.
  9. Close the view details box and press the Next button.

Configure migration settings

  1. Specify your target SQL Server on Azure Virtual Machine by selecting your subscription, location, resource group from the corresponding drop-down lists and then select Next.
  2. Select Online migration as the migration mode.

    Note

    In the online migration mode, the source SQL Server database can be used for read and write activity while database backups are continuously restored on the target SQL Server on Azure Virtual Machine. Application downtime is limited to duration for the cutover at the end of migration.

  3. In step 5, select the location of your database backups. Your database backups can either be located on an on-premises network share or in an Azure storage blob container.

    Note

    If your database backups are provided in an on-premises network share, DMS will require you to setup self-hosted integration runtime in the next step of the wizard. Self-hosted integration runtime is required to access your source database backups, check the validity of the backup set and upload them to Azure storage account.
    If your database backups are already on an Azure storage blob container, you do not need to setup self-hosted integration runtime.

  • For backups located on a network share provide the below details of your source SQL Server, source backup location, target database name and Azure storage account for the backup files to be uploaded to.

    Field Description
    Source Credentials - Username The credential (Windows / SQL authentication) to connect to the source SQL Server instance and validate the backup files.
    Source Credentials - Password The credential (Windows / SQL authentication) to connect to the source SQL Server instance and validate the backup files.
    Network share location that contains backups The network share location that contains the full and transaction log backup files. Any invalid files or backups files in the network share that don't belong to the valid backup set will be automatically ignored during the migration process.
    Windows user account with read access to the network share location The Windows credential (username) that has read access to the network share to retrieve the backup files.
    Password The Windows credential (password) that has read access to the network share to retrieve the backup files.
    Target database name The target database name can be modified if you wish to change the database name on the target during the migration process.
  • For backups stored in an Azure storage blob container specify the below details of the Target database name, Resource group, Azure storage account, Blob container from the corresponding drop-down lists.

    Field Description
    Target database name The target database name can be modified if you wish to change the database name on the target during the migration process.
    Storage account details The resource group, storage account and container where backup files are located.
  1. Select Next to continue.

    Important

    If loopback check functionality is enabled and the source SQL Server and file share are on the same computer, then source won't be able to access the files hare using FQDN. To fix this issue, disable loopback check functionality using the instructions here

Create Azure Database Migration Service

  1. Create a new Azure Database Migration Service or reuse an existing Service that you previously created.

    Note

    If you had previously created DMS using the Azure Portal, you cannot reuse it in the migration wizard in Azure Data Studio. Only DMS created previously using Azure Data Studio can be reused.

  2. Select the Resource group where you have an existing DMS or need to create a new one. The Azure Database Migration Service dropdown will list any existing DMS in the selected resource group.
  3. To reuse an existing DMS, select it from the dropdown list and the status of the self-hosted integration runtime will be displayed at the bottom of the page.
  4. To create a new DMS, select on Create new.
  5. On the Create Azure Database Migration Service, screen provide the name for your DMS and select Create.
  6. After successful creation of DMS, you'll be provided with details to Setup integration runtime.
  7. Select on Download and install integration runtime to open the download link in a web browser. Complete the download. Install the integration runtime on a machine that meets the pre-requisites of connecting to source SQL Server and the location containing the source backup.
  8. After the installation is complete, the Microsoft Integration Runtime Configuration Manager will automatically launch to begin the registration process.
  9. Copy and paste one of the authentication keys provided in the wizard screen in Azure Data Studio. If the authentication key is valid, a green check icon is displayed in the Integration Runtime Configuration Manager indicating that you can continue to Register.
  10. After successfully completing the registration of self-hosted integration runtime, close the Microsoft Integration Runtime Configuration Manager and switch back to the migration wizard in Azure Data Studio.
  11. Select Test connection in the Create Azure Database Migration Service screen in Azure Data Studio to validate that the newly created DMS is connected to the newly registered self-hosted integration runtime and select Done. Test connection integration runtime
  12. Review the summary and select Done to start the database migration.

Monitor your migration

  1. On the Database Migration Status, you can track the migrations in progress, migrations completed, and migrations failed (if any).

    monitor migration dashboard

  2. Select Database migrations in progress to view ongoing migrations and get further details by selecting the database name.

  3. The migration details page displays the backup files and the corresponding status:

    Status Description
    Arrived Backup file arrived in the source backup location and validated
    Uploading Integration runtime is currently uploading the backup file to Azure storage
    Uploaded Backup file is uploaded to Azure storage
    Restoring Azure Database Migration Service is currently restoring the backup file to SQL Server on Azure Virtual Machine
    Restored Backup file is successfully restored on SQL Server on Azure Virtual Machine
    Canceled Migration process was canceled
    Ignored Backup file was ignored as it doesn't belong to a valid database backup chain

    online vm backup restore details

Complete migration cutover

The final step of the tutorial is to complete the migration cutover. The completion ensures the migrated database in SQL Server on Azure Virtual Machine is ready for use. Downtime is required for applications that connect to the database and the timing of the cutover needs to be carefully planned with business or application stakeholders.

To complete the cutover:

  1. Stop all incoming transactions to the source database.
  2. Make application configuration changes to point to the target database in SQL Server on Azure Virtual Machine.
  3. Take any tail log backups for the source database in the backup location specified.
  4. Ensure all database backups have the status Restored in the monitoring details page.
  5. Select Complete cutover in the monitoring details page.

During the cutover process, the migration status changes from in progress to completing. The migration status changes to succeeded when the cutover process is completed. The database migration is successful and that the migrated database is ready for use.

Next steps