Hi Mark Taylor,
Greetings!!
When you start an offline migration using Azure Database Migration Service (DMS):
Your source SQL Server database remains fully operational it is not disabled, set to read-only, or taken offline automatically.
The term “downtime” refers to the period during which you must stop any new data changes (writes) to the source database. This is essential because any changes made after migration starts will not be included, potentially leading to data inconsistencies.
Your plan is solid and aligns with best practices:
Migrate a copy of your database to Azure SQL Database.
Test your application against the migrated copy to ensure functionality and performance.
Once satisfied:
Stop all activity on the source database.
Optionally, re-run the migration to capture any final changes.
Reconfigure your application to point to the new Azure SQL Database.
For more information, please refer the documents:
https://learn.microsoft.com/en-us/azure/dms/faq?utm_source=chatgpt.com#how-can-i-ensure-that-dms-has-migrated-all-the-data-from-the-source-database-to-azure-sql-targets-https://techcommunity.microsoft.com/blog/microsoftdatamigration/introducing-azure-sql-database-offline-migrations-for-the-azure-sql-migration-ex/3655381?utm_source=chatgpt.com
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.