| title | Monitor and troubleshoot data migration | ||
|---|---|---|---|
| description | Monitor and troubleshoot data migration (Stretch Database) | ||
| author | MikeRayMSFT | ||
| ms.author | mikeray | ||
| ms.reviewer | randolphwest | ||
| ms.date | 07/25/2022 | ||
| ms.service | sql-server-stretch-database | ||
| ms.topic | conceptual | ||
| ms.custom | seo-dt-2019 | ||
| helpviewer_keywords |
|
[!INCLUDE sqlserver2016-windows-only]
Important
Stretch Database is deprecated in [!INCLUDE sssql22-md]. [!INCLUDE ssNoteDepFutureAvoid-md]
Open the dynamic management view sys.dm_db_rda_migration_status to see how many batches and rows of data have been migrated. For more info, see sys.dm_db_rda_migration_status (Transact-SQL).
There are several problems that can affect migration. Check the following things.
-
Check network connectivity for the SQL Server computer.
-
Check that the Azure firewall isn't blocking your SQL Server from connecting to the remote endpoint.
-
Check the dynamic management view
sys.dm_db_rda_migration_statusfor the status of the latest batch. If an error has occurred, check the error_number, error_state, and error_severity values for the batch.-
For more info about the view, see sys.dm_db_rda_migration_status (Transact-SQL).
-
For more info about the content of a SQL Server error message, see sys.messages (Transact-SQL).
-
You may have to add a rule in the Azure firewall settings of the Azure server to let SQL Server communicate with the remote Azure server.