Skip to content

Commit e2db2be

Browse files
committed
Add 3
1 parent f51a2d2 commit e2db2be

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/dms/migrate-azure-mysql-consistent-backup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,6 @@ With this feature, we don't take a read lock on the server. We instead read tabl
2828
Key features of Consistent Snapshot without locks:
2929
*Ability to support heavy workload servers or servers with long-running transactions without the need for read locks.
3030
*Resilient in completing migrations even in the event of failures caused by transient network/server blips that result in loss of all the precreated connections.
31-
*Ability to resume migrations upon Data Migration Service (DMS) agent upgrades or restarts.
3231

3332
### Enable Consistent Snapshot with read lock (GA)
3433

@@ -58,6 +57,7 @@ To complete the migration successfully with Consistent Snapshot with read lock e
5857
## Known issues and limitations for Enable Consistent Snapshot without locks
5958

6059
- Tables with foreign keys having Cascade or Set Null on delete/on update clause aren't supported.
60+
- No DDL changes should occur during initial load.
6161

6262
## Known issues and limitations for Enable Consistent Snapshot with read lock
6363

0 commit comments

Comments
 (0)