Merge pull request #257599 from aditivgupta/DDL

changes

Author: prmerger-automator[bot]

articles/dms/concepts-migrate-azure-mysql-replicate-changes.md

@@ -51,7 +51,7 @@ To complete the replicate changes migration successfully, ensure that the follow
 
 - When performing a replicate changes migration, the name of the database on the target server must be the same as the name on the source server.
 - Support is limited to the ROW binlog format.
-- DDL changes replication is supported only when you have selected the option for migrating entire server on DMS UI.
+- DDL changes replication is supported only when migrating to a v8.0 Azure Database for MySQL Flexible Server target server and when you have selected the option for **Replicate data definition and administration statements for selected objects** on DMS UI. The replication feature supports replicating data definition and administration statements that occur after the initial load and are logged in the binary log to the target.
 - Renaming databases or tables is not supported when replicating changes.
 
 ## Next steps

articles/dms/tutorial-mysql-azure-external-to-flex-online-portal.md

@@ -64,7 +64,20 @@ As you prepare for the migration, be sure to consider the following limitations.
 * Currently, DMS doesn't support migrating the DEFINER clause for objects. All object types with definers on the source are dropped and after the migration, the default definer for all objects that support a definer clause and that are created during schema migration, will be set to the login used to run the migration.
 * Currently, DMS only supports migrating a schema as part of data movement. If nothing is selected for data movement, the schema migration won't occur. Note that selecting a table for schema migration also selects it for data movement.
 * Online migration support is limited to the ROW binlog format.
-* Online migration only replicates DML changes; replicating DDL changes isn't supported. Don't make any schema changes to the source while replication is in progress, if DMS detects DDL while replicating, it will generate a warning that can be viewed in the Azure portal.
+* Online migration now supports DDL statement replication when migrating to a v8.0 Azure Database for MySQL Flexible Server target server. For target server engine version v5.x, DDL statement replication is not supported currently.
+  * Statement replication is supported for databases, tables, and schema objects (views, routines, triggers) selected for schema migration when configuring an Azure DMS migration activity. Data definition and administration statements for databases, tables, and schema objects that aren’t selected won’t be replicated. Selecting an entire server for migration will replicate statements for any tables, databases, and schema objects that are created on the source server after the initial load has completed.
+  * Azure DMS statement replication supports all of the Data Definition statements listed [here](https://dev.mysql.com/doc/refman/8.0/en/sql-data-definition-statements.html), with the exception of the following commands:
+    • LOGFILE GROUP statements
+    • SERVER statements
+    • SPATIAL REFERENCE SYSTEM statements
+    • TABLESPACE statements
+  * Azure DMS statement replication supports all of the Data Administration – Account Management statements listed [here](https://dev.mysql.com/doc/refman/8.0/en/account-management-statements.html), with the exception of the following commands:
+    * SET DEFAULT ROLE
+    * SET PASSWORD
+  * Azure DMS statement replication supports all of the Data Administration – Table Maintenance statements listed [here](https://dev.mysql.com/doc/refman/8.0/en/table-maintenance-statements.html), with the exception of the following commands:
+    * REPAIR TABLE
+    * ANALYZE TABLE
+    * CHECKSUM TABLE
 
 ## Best practices for creating a flexible server for faster data loads using DMS
 

articles/dms/tutorial-mysql-azure-single-to-flex-online-portal.md

@@ -65,7 +65,20 @@ As you prepare for the migration, be sure to consider the following limitations.
 * Currently, DMS doesn't support migrating the DEFINER clause for objects. All object types with definers on the source are dropped and after the migration, the default definer for all objects that support a definer clause and that are created during schema migration, will be set to the login used to run the migration.
 * Currently, DMS only supports migrating a schema as part of data movement. If nothing is selected for data movement, the schema migration won't occur. Note that selecting a table for schema migration also selects it for data movement.
 * Online migration support is limited to the ROW binlog format.
-* Online migration only replicates DML changes; replicating DDL changes isn't supported. Don't make any schema changes to the source while replication is in progress, if DMS detects DDL while replicating, it will generate a warning that can be viewed in the Azure portal.
+* Online migration now supports DDL statement replication when migrating to a v8.0 Azure Database for MySQL Flexible Server target server. For target server engine version v5.x, DDL statement replication is not supported currently.
+  * Statement replication is supported for databases, tables, and schema objects (views, routines, triggers) selected for schema migration when configuring an Azure DMS migration activity. Data definition and administration statements for databases, tables, and schema objects that aren’t selected won’t be replicated. Selecting an entire server for migration will replicate statements for any tables, databases, and schema objects that are created on the source server after the initial load has completed.
+  * Azure DMS statement replication supports all of the Data Definition statements listed [here](https://dev.mysql.com/doc/refman/8.0/en/sql-data-definition-statements.html), with the exception of the following commands:
+    • LOGFILE GROUP statements
+    • SERVER statements
+    • SPATIAL REFERENCE SYSTEM statements
+    • TABLESPACE statements
+  * Azure DMS statement replication supports all of the Data Administration – Account Management statements listed [here](https://dev.mysql.com/doc/refman/8.0/en/account-management-statements.html), with the exception of the following commands:
+    * SET DEFAULT ROLE
+    * SET PASSWORD
+  * Azure DMS statement replication supports all of the Data Administration – Table Maintenance statements listed [here](https://dev.mysql.com/doc/refman/8.0/en/table-maintenance-statements.html), with the exception of the following commands:
+    * REPAIR TABLE
+    * ANALYZE TABLE
+    * CHECKSUM TABLE
 
 ## Best practices for creating a flexible server for faster data loads using DMS