Azure Database Migration Service (ADMS) supports Schema and Data migration from different database technologies to the Azure platform. This article will shed some light on validations, limits, and use cases of migration tasks for SQL Server (RDS & On-Premises) to Azure cloud database with ADMS.

Before creating a first migration project in ADMS, let’s get familiar with the basic requirements of the Azure Database Migration Service.

We can create a migration project in the ADMS with migration parameters chosen only. While adding the project, it asks to select the migration activity type.

There are three primary activity types available on the Azure portal:

Schema Only Migration

The migration project will sync the schema only. For synchronizing the data, users have to create a separate project/activity with Offline Data Migration or Online Data Migration.

Offline Data Migration

Data will be synchronized from source to destination when the user triggers the event. Here, “Offline” defines when the data will be synchronized, and when users execute the migration task.

Online Data Migration

Data synchronization continues between the source and the destination, using CDC or Replication. Before setting up the source and destination, you should enable the source database server with replication (Distribution database configuration).

Create Project Only

It’s the default option taking place when the migration type is not defined while creating a project. This way, you can create a project now and determine the migration task later.

#microsoft azure #programming #azure sql #database administration #sql server