Merge pull request #275182 from aditivgupta/s2f

Update

Author: prmerger-automator[bot]

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

@@ -84,6 +84,7 @@ As you prepare for the migration, be sure to consider the following limitations.
     * ANALYZE TABLE
     * CHECKSUM TABLE
   * Azure DMS statement or binlog replication does not support the following syntax: ‘CREATE TABLE `b` as SELECT * FROM `a`;’. The replication of this DDL will result in the following error: “Only BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.”
+* Migration duration can be affected by compute maintenance on the backend, which can reset the progress.
 
 ## Best practices for creating a flexible server for faster data loads using DMS
 

articles/mysql/migrate/migrate-single-flexible-in-place-auto-migration.md

@@ -55,6 +55,7 @@ Following described are the ways to review your migration schedule once you rece
 * The MySQL engine doesn't guarantee any sort order if there's no 'SORT' clause present in queries. Post in-place automigration, you may observe a change in the sort order. If preserving sort order is crucial, ensure your queries are updated to include 'SORT' clause before the scheduled in-place automigration.
 * If your source Azure Database for MySQL Single Server has engine version v8.x, ensure to upgrade your source server's .NET client driver version to 8.0.32 to avoid any encoding incompatibilities post migration to Flexible Server.
 * If your source Azure Database for MySQL Single Server has firewall rule names exceeding 80 characters, rename them to ensure length of name is fewer than 80 characters. (The firewall rule name length supported on Flexible Server is 80 characters whereas on Single Server the allowed length is 12 8 characters.)
+* If your source Azure Database for MySQL Single Server utilizes non-default ports such as 3308,3309 and 3310, change your connectivity port to 3306 as the above mentioned non-default ports are not supported on Flexible Server.
 
 ## How is the target MySQL Flexible Server auto-provisioned?
 

articles/mysql/migrate/migrate-single-flexible-mysql-import-cli.md

@@ -64,6 +64,7 @@ az account set --subscription <subscription id>
 - If the Single Server instance has ' Infrastructure Double Encryption' enabled, enabling Customer Managed Key (CMK) on target Flexible Server instance is recommended to support similar functionality. You can choose to enable CMK on target server with Azure Database for MySQL Import CLI input parameters or post migration as well.
 - If the Single Server instance has 'Query Store' enabled, enabling slow query logs on target Flexible Server instance is recommended to support similar functionality. You can configure slow query logs on the target flexible server by following steps [here](/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](/azure/mysql/flexible-server/tutorial-query-performance-insights#view-query-insights-by-using-workbooks).
 - If your Single Server instance has Legacy Storage architecture (General Purpose storage V1), you need to set the parameter log_bin=ON for your Single Server instance before initiating the import operation. In order to do so, create a read replica for your Single Server instance and then delete it. This operation will set the parameter log_bin to ON and you can then trigger an import operation to migrate to Flexible Server.
+- If your Single Server instance has Advanced Threat Protection enabled, you need to enable Advanced Threat Protection on the migrated Flexible Server instance post migration by following steps [here] (/azure/mysql/flexible-server/advanced-threat-protection-setting?view=azure-cli-latest).
 - If your Single Server instance has engine version v8.0, consider performing the following actions to avoid any breaking changes due to community minor version differences between the Single and Flexible Server instance :
 
   - Run the following statement to check if your instance could be impacted by erroneous histogram information. If the corresponding tables are output, we recommend that you refer to [https://dev.mysql.com/blog-archive/histogram-statistics-in-mysql/](https://dev.mysql.com/blog-archive/histogram-statistics-in-mysql/) to delete the histogram information, and then recreate it on the Flexible Server. It's worth noting that the histogram inf` is only statistical information about the columns, and this information only exists in system tables, so deleting the histogram info will not affect the table data.
@@ -238,7 +239,7 @@ CALL mysql.az_show_binlog_file_and_pos_for_mysql_import();
 
 ## How long does Azure Database for MySQL Import take to migrate my Single Server instance?
 
-Below is the benchmarked performance based on storage size.
+Below is the benchmarked performance based on storage size for General Purpose V2 storage architecture. (Servers with General purpose V1 storage will take longer time to migrate as it involves upgrading the storage architecture as well)
 
   | Single Server Storage Size | Import time |
   | ------------- |:-------------:|

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

@@ -189,7 +189,11 @@ After the forced migration, you must reconfigure the features listed above on th
 
 **Q. Is there cross-version support?**
 
-Yes, migration from lower version MySQL servers (v5.6 and above) to higher versions is supported through Azure Database Migration Service migrations.
+**A.** Yes, migration from lower version MySQL servers (v5.6 and above) to higher versions is supported through Azure Database Migration Service migrations.
+
+**Q. MyAzure Database for MySQL Single Server utilizes non-default ports such as 3308,3309 and 3310, which is not supported on Flexible Server. What should I do to ensure connectivity when migrating to Flexible Server?**
+
+**A.** If your source Azure Database for MySQL Single Server utilizes non-default ports such as 3308,3309 and 3310, change your connectivity port to 3306 as the above mentioned non-default ports are not supported on Flexible Server.
 
 **Q. I have further questions on retirement. How can I get assistance around it?**