Skip to content

Commit 398c005

Browse files
committed
Up 2
1 parent e922670 commit 398c005

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,10 @@ To complete the migration successfully with Consistent Snapshot with read lock e
5353
5454
- Configure the **binlog_expire_logs_seconds** parameter on the source server to ensure that binlog files are not purged before the replica commits the changes. Post successful cutover, the value can be reset.
5555

56+
## Known issues and limitations for Enable Consistent Snapshot without locks
57+
58+
- Tables with foreign keys having Cascade or Set Null on delete/on update clause are not supported.
59+
5660
## Known issues and limitations for Enable Consistent Snapshot with read lock
5761

5862
The known issues and limitations associated with Consistent Backup fall broadly into two categories: locks and retries.

0 commit comments

Comments
 (0)