Merge pull request #268294 from aditivgupta/sbsimport

Push

Author: v-dirichards

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

@@ -76,16 +76,17 @@ Following described are the ways to review your migration schedule once you have
 * For Single Servers with less than 20 GiB storage, the storage size is set to 20 GiB as that is the minimum storage limit on Azure Database for MySQL - Flexible Server.
 * Both username formats – username@server_name (Single Server) and username (Flexible Server) are supported on the migrated Flexible Server.
 * Both connection string formats – Single Server and Flexible Server are supported on the migrated Flexible Server.
+* For Single Server instance with Query store enabled, the server parameter 'slow_query_log' on target instance is set to ON to ensure feature parity when migrating to Flexible Server. Please note, for certain workloads this could impact performance and if you observe any performance degradation, set this server parameter to 'OFF' on the Flexible Server instance.
 
 ## Post-migration steps
 
 > [!NOTE]
 > Post-migration do no restart the stopped Single Server instance as it may hamper your client's and application connectivity.
 
-Copy the following properties from the source Single Server to target Flexible Server post in-place migration operation is completed successfully:
-
-* Monitoring page settings (Alerts, Metrics, and Diagnostic settings)
-* Any Terraform/CLI scripts you host to manage your Single Server instance should be updated with Flexible Server references.
+* Copy the following properties from the source Single Server to target Flexible Server post in-place migration operation is completed successfully:
+  * Monitoring page settings (Alerts, Metrics, and Diagnostic settings)
+  * Any Terraform/CLI scripts you host to manage your Single Server instance should be updated with Flexible Server references.
+* For Single Server instance with Query store enabled, the server parameter 'slow_query_log' on target instance is set to ON to ensure feature parity when migrating to Flexible Server. Please note, for certain workloads this could impact performance and if you observe any performance degradation, set this server parameter to 'OFF' on the Flexible Server instance.
 
 ## Frequently Asked Questions (FAQs)
 
@@ -99,7 +100,7 @@ Copy the following properties from the source Single Server to target Flexible S
 
 **Q. How can I set up or view in-place migration alerts?​**
 
-**A.** Following are the ways you can set up alerts :
+**A.** Following are the ways you can set up alerts:
 
 * Configure service health alerts to receive in-place migration schedule and progress notifications via email/SMS by following steps [here](../single-server/concepts-planned-maintenance-notification.md#to-receive-planned-maintenance-notification).
 * Check the in-place migration notification on the Azure portal by following steps [here](../single-server/concepts-planned-maintenance-notification.md#check-planned-maintenance-notification-from-azure-portal).
@@ -110,7 +111,7 @@ Copy the following properties from the source Single Server to target Flexible S
 
 **Q. What are some post-migration activities I need to perform?​**
 
-**A.** Following are some post-migration activities :
+**A.** Following are some post-migration activities:
 
 * Monitoring page settings (Alerts, Metrics, and Diagnostic settings)
 * Any Terraform/CLI scripts you host to manage your Single Server instance should be updated with Flexible Server references.

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

@@ -28,7 +28,7 @@ This tutorial shows how to use the Azure Database for MySQL Import CLI command t
 
 ## What's new?
 
-- Azure Database for MySQL Import operation for Single Servers with Legacy Storage architecture (General Purpose storage V1) is now supported. (Feb 2024)
+- Azure Database for MySQL Import operation for Single Servers with Legacy Storage architecture (General Purpose storage V1) is now supported. You need to set the parameter log_bin=ON for your Single Server instance with Legacy Storage 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. (Feb 2024)
 
 ## Launch Azure Cloud Shell
 
@@ -63,6 +63,7 @@ az account set --subscription <subscription id>
 - For CMK enabled Single Server instances, Azure Database for MySQL Import command requires you to provide mandatory input parameters for enabling CMK on target Flexible Server.
 - 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.
 - Only instance-level import is supported. No option to import selected databases within an instance is provided.
 - Below items should be copied from source to target by the user post the Import operation:
   - Read-Replicas
@@ -108,7 +109,7 @@ az mysql flexible-server import create --data-source-type
                                 [--zone]
 ```
 
-The following example takes in the data source information for Single Server named 'test-single-server' and target Flexible Server information, creates a target Flexible Server named `test-flexible-server` in the `westus` location (same location as that of the source Single Server) and performs an import from source to target. Azure Database MySQL Import command maps over the corresponding tier, version, sku-name, storage-size, location, geo-redundant-backup, public-access, tags, auto grow, backup-retention-days, admin-user and admin-password  properties from Single Server to Flexible Server as smart defaults if no inputs are provided to the CLI command. You can chose to override the smart defaults by providing inputs for these optional parameters.
+The following example takes in the data source information for Single Server named 'test-single-server' and target Flexible Server information, creates a target Flexible Server named `test-flexible-server` in the `westus` location (same location as that of the source Single Server) and performs an import from source to target. Azure Database MySQL Import command maps over the corresponding tier, version, sku-name, storage-size, location, geo-redundant-backup, public-access, tags, auto grow, backup-retention-days, admin-user and admin-password  properties from Single Server to Flexible Server as smart defaults if no inputs are provided to the CLI command. You can choose to override the smart defaults by providing inputs for these optional parameters.
 
 ```azurecli-interactive
 az mysql flexible-server import create --data-source-type "mysql_single" --data-source "test-single-server" --resource-group "test-rg"  --name "test-flexible-server"
@@ -170,7 +171,7 @@ tier | Burstable | Compute tier of the target Azure Database for MySQL Flexible
 public-access | 0.0.0.0 | Determines the public access for the target Azure Database for MySQL Flexible Server. Enter single or range of IP addresses to be included in the allowed list of IPs. IP address ranges must be dash-separated and not contain any spaces. Specifying 0.0.0.0 allows public access from any resources deployed within Azure to access your server. Setting it to "None" sets the server in public access mode but doesn't create a firewall rule.
 vnet | myVnet | Name or ID of a new or existing virtual network. If you want to use a vnet from different resource group or subscription, please provide a resource ID. The name must be between 2 to 64 characters. The name must begin with a letter or number, end with a letter, number or underscore, and may contain only letters, numbers, underscores, periods, or hyphens.
 subnet | mySubnet | Name or resource ID of a new or existing subnet. If you want to use a subnet from different resource group or subscription, please provide resource ID instead of name. Please note that the subnet will be delegated to flexibleServers. After delegation, this subnet cannot be used for any other type of Azure resources.
-private-dns-zone | myserver.private.contoso.com | The name or id of new or existing private dns zone. You can use the private dns zone from same resource group, different resource group, or different subscription. If you want to use a zone from different resource group or subscription, please provide resource Id. CLI creates a new private dns zone within the same resource group as virtual network if not provided by users.
+private-dns-zone | myserver.private.contoso.com | The name or ID of new or existing private dns zone. You can use the private dns zone from same resource group, different resource group, or different subscription. If you want to use a zone from different resource group or subscription, please provide resource ID. CLI creates a new private dns zone within the same resource group as virtual network if not provided by users.
 key | key identifier of testKey | The resource ID of the primary keyvault key for data encryption.
 identity | testIdentity | The name or resource ID of the user assigned identity for data encryption.
 storage-size | 32 | The storage capacity of the target Azure Database for MySQL Flexible Server. The minimum is 20 GiB, and max is 16 TiB.
@@ -184,7 +185,7 @@ iops | 500 | Number of IOPS to be allocated for the target Azure Database for My
 
 ## Steps for online migration
 
-After completing the above-stated Azure Database for MySQL Import operation :
+After completing the above-stated Azure Database for MySQL Import operation:
 
 - Log in to the target Azure Database for MySQL Flexible Server and run the following command to get the bin-log filename and position corresponding to the backup snapshot used by Azure Database for MySQL Import CLI to restore to the target server.