Monitor migration activity using the Azure Database Migration Service

In this article, you learn how to monitor the progress of a migration at both a database level and a table level.

Monitor at the database level

To monitor activity at the database level, view the database-level blade:

Note

Selecting the database hyperlink will show you the list of tables and their migration progress.

The following table lists the fields on the database-level blade and describes the various status values associated with each.

Field name	Field substatus	Description
Activity status	Running	Migration activity is running.
	Succeeded	Migration activity succeeded without issues.
	Faulted	Migration failed. Select the ‘See error details’ link under migration details for the complete error message.
Status	Initializing	DMS is setting up the migration pipeline.
	Running	DMS pipeline is running and performing migration.
	Complete	Migration completed.
	Failed	Migration failed. Click on migration details to see migration errors.
Migration details	Initiating the migration pipeline	DMS is setting up the migration pipeline.
	Full data load in progress	DMS is performing initial load.
	Ready for Cutover	After initial load is completed, DMS will mark database as ready for cutover. User should check if data has caught up on continuous sync.
	All changes applied	Initial load and continuous sync are complete. This status also occurs after the database is cutover successfully.
	See error details	Click on the link to show error details.
Duration	N/A	Total time from migration activity being initialized to migration completed or migration faulted.

Monitor at table level – Quick Summary

To monitor activity at the table level, view the table-level blade. The top portion of the blade shows the detailed number of rows migrated in full load and incremental updates.

The bottom portion of the blade lists the tables and shows a quick summary of migration progress.

The following table describes the fields shown in the table-level details.

Field name	Description
Full load completed	Number of tables completed full data load.
Full load queued	Number of tables being queued for full load.
Full load loading	Number of tables failed.
Incremental updates	Number of change data capture (CDC) updates in rows applied to target.
Incremental inserts	Number of CDC inserts in rows applied to target.
Incremental deletes	Number of CDC deletes in rows applied to target.
Pending changes	Number of CDC in rows that are still waiting to get applied to target.
Applied changes	Total of CDC updates, inserts, and deletes in rows applied to target.
Tables in error state	Number of tables that are in ‘error’ state during migration. Some examples that tables can go into error state are when there are duplicates identified in the target or data isn't compatible loading in the target table.

Monitor at table level – Detailed Summary

There are two tabs that show migration progress in Full load and Incremental data sync.

The following table describes the fields shown in table level migration progress.

Field name	Description
Status - Syncing	Continuous sync is running.
Insert	Number of CDC inserts in rows applied to target.
Update	Number of CDC updates in rows applied to target.
Delete	Number of CDC deletes in rows applied to target.
Total Applied	Total of CDC updates, inserts, and deletes in rows applied to target.
Data Errors	Number of data errors happened in this table. Some examples of the errors are 511: Cannot create a row of size %d which is greater than the allowable maximum row size of %d, 8114: Error converting data type %ls to %ls. Customer should query from dms_apply_exceptions table in Azure target to see the error details.

Note

CDC values of Insert, Update and Delete and Total Applied may decrease when database is cutover or migration is restarted.

Next steps

• Review the migration guidance in the Microsoft Database Migration Guide.