Skip to content

Commit 7b1b3f5

Browse files
authored
Update tutorial-sql-server-to-virtual-machine-offline-ads.md
1 parent 19dec25 commit 7b1b3f5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/dms/tutorial-sql-server-to-virtual-machine-offline-ads.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ To complete this tutorial, you need to:
105105
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**.
106106
2. Select **Offline migration** as the migration mode.
107107
> [!NOTE]
108-
> In the offline migration mode, the source SQL Server database is not available for write activity while database backup files are restored on the target Azure SQL database. Application downtime persists through the start until the completion of the migration process.
108+
> In the offline migration mode, the source SQL Server database should not be used for write activity while database backup files are restored on the target Azure SQL database. Application downtime persists through the start until the completion of the migration process.
109109
3. 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.
110110
> [!NOTE]
111111
> 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.<br/> If your database backups are already on an Azure storage blob container, you do not need to setup self-hosted integration runtime.

0 commit comments

Comments
 (0)