Merge pull request #250458 from aditivgupta/toperror

Toperror

Author: prmerger-automator[bot]

articles/dms/known-issues-azure-mysql-fs-online.md

@@ -16,14 +16,14 @@ Known issues associated with migrations to Azure Database for MySQL are describe
 
 ## Schema Migration Issue for v8.0 MySQL Flexible Server target
 
-- **Error**: Fatal error migrating the source's schema to target MySQL Flexible Server with engine version 8.0. This error indicates that the server parameter sql_generate_invisible_primary_key for target MySQL Flexible Server  has been set to ON.
+- **Error**: A migration to a MySQL Flexible Server with engine version 8.0.30 or higher can fail when the feature to generate invisible primary keys for InnoDB tables is enabled (see [MySQL :: MySQL 8.0 Reference Manual :: 13.1.20.11 Generated Invisible Primary Keys](https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html)).  The failure may occur when migrating table schema from the source to the target, when applying changes during the replication phase of online migrations, when retrying a migration, or when migrating to a target where the schema has been migrated manually.
 
-  **Potential error message**: 
+  **Potential error message**:
   - "Unknown error."
   - "Failed to generate invisible primary key. Auto-increment column already exists."
   - "The column 'my_row_id' in the target table 'table name' in database 'database' does not exist on the source table."
 
-  **Limitation**: This error occurs during the schema migration phase or change data capture phase, if the schema migration option has been selected for the DMS migration project and the server parameter sql_generate_invisible_primary_key for target MySQL Flexible Server has been set to ON.
+  **Limitation**: Migration to MySQL Flexible Server instance where sql_generate_invisible_primary_key is enabled is not supported by DMS.
 
   **Workaround**: Set the server parameter sql_generate_invisible_primary_key for target MySQL Flexible Server to OFF. The server parameter can be found in the Server parameters Blade under the All tab for the target MySQL Flexible Server. Additionally, drop the target database and start over the DMS migration to not have any mismatched schemas.
 

articles/mysql/single-server/whats-happening-to-mysql-single-server.md

@@ -38,7 +38,7 @@ Learn how to migrate from Azure Database for MySQL - Single Server to Azure Data
 For more information on migrating from Single Server to Flexible Server using other migration tools, visit [Select the right tools for migration to Azure Database for MySQL](../migrate/how-to-decide-on-right-migration-tools.md).
 
 > [!NOTE]
-> In-place auto-migration from Azure Database for MySQL – Single Server to Flexible Server is a service-initiated in-place migration during planned maintenance window for Single Server database workloads with Basic or General Purpose SKU, data storage used < 10 GiB and no complex features enabled. The eligible servers are identified by the service and are sent an advance notification detailing steps to review migration details. All other Single Server workloads are recommended to use user-initiated migration tooling offered by Azure - Azure DMS, Azure MySQL Import to migrate. Learn more about in-place auto-migration [here](../migrate/migrate-single-flexible-in-place-auto-migration.md).
+> In-place auto-migration from Azure Database for MySQL – Single Server to Flexible Server is a service-initiated in-place migration during planned maintenance window for Single Server database workloads with Basic or General Purpose SKU, data storage used < 10 GiB and no complex features (CMK, AAD, Read Replica, Private Link) enabled. The eligible servers are identified by the service and are sent an advance notification detailing steps to review migration details. All other Single Server workloads are recommended to use user-initiated migration tooling offered by Azure - Azure DMS, Azure MySQL Import to migrate. Learn more about in-place auto-migration [here](../migrate/migrate-single-flexible-in-place-auto-migration.md).
 
 ## Migration Eligibility
 
@@ -47,7 +47,7 @@ To upgrade to Azure Database for MySQL Flexible Server, it's important to know w
 | Single Server configuration not supported in Flexible Server | How and when to migrate? |
 |---------------------------------------------------------|--------------------------|
 | Single servers with Private Link enabled | Private Link for flexible server is available now, and you can start migrating your single server. |
-| Single servers with Cross-Region Read Replicas enabled | Cross-Region Read Replicas for flexible server (for paired region) is available now, and you can start migrating your single server. |
+| Single servers with Cross-Region Read Replicas enabled | Cross-Region Read Replicas for flexible server is available now, and you can start migrating your single server. |
 | Single servers with Query Store enabled | You are eligible to migrate and you can configure slow query logs on the target flexible server by following steps [here](https://learn.microsoft.com/azure/mysql/flexible-server/tutorial-query-performance-insights#configure-slow-query-logs-by-using-the-azure-portal). You can then view query insights by using [workbooks template](https://learn.microsoft.com/azure/mysql/flexible-server/tutorial-query-performance-insights#view-query-insights-by-using-workbooks). |
 | Single server deployed in regions where flexible server isn't supported (Learn more about regions [here](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?regions=all&products=mysql)). | Azure Database Migration Service (classic) supports cross-region migration. Deploy your target flexible server in a suitable region and migrate using DMS (classic). |
 
@@ -119,7 +119,7 @@ To upgrade to Azure Database for MySQL Flexible Server, it's important to know w
 
 **Q. I have cross-region read replicas configured for my single server, and this feature is not currently supported in Flexible Server. How do I migrate?**
 
-**A.**  Cross-Region Read Replicas for flexible server (for paired region) is available now, and you can start migrating your single server.
+**A.**  Cross-Region Read Replicas for flexible server is available now, and you can start migrating your single server.
 
 **Q. I have TLS v1.0/1.1 configured for my v8.0 single server, and this feature is not currently supported in Flexible Server. How do I migrate?**