Skip to content

Commit 8bf17f3

Browse files
authored
Merge pull request #101955 from ramakoni1/patch-3
Clarification on concurrent db migration per subscription.
2 parents 8004ac4 + 1128677 commit 8bf17f3

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/dms/tutorial-mysql-azure-mysql-online.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -220,6 +220,8 @@ After the service is created, locate it within the Azure portal, open it, and th
220220
If the target database contains the same database name as the source database, Azure Database Migration Service selects the target database by default.
221221
222222
![Map to target databases](media/tutorial-mysql-to-azure-mysql-online/dms-map-target-details.png)
223+
> [!NOTE]
224+
> Though you can select multiple databases in this step, each instance of Azure Database Migration Service supports up to four databases for concurrent migration. Also, there is a limit of two instances of Azure Database Migration Service per region in a subscription. For example, if you have 40 databases to migrate, you can only migrate eight of them concurrently, and only if you have created two instances of Azure Database Migration Service.
223225
224226
3. Select **Save**, on the **Migration summary** screen, in the **Activity name** text box, specify a name for the migration activity, and then review the summary to ensure that the source and target details match what you previously specified.
225227

0 commit comments

Comments
 (0)