Merge pull request #275243 from MicrosoftDocs/release-build-2024mysql

[Build 2024 ship room] MySQL releases for //build 2024

Author: WendyRing

articles/mysql/flexible-server/concepts-accelerated-logs.md

@@ -1,52 +1,43 @@
 ---
-title: Accelerated logs
-description: This article describes the accelerated logs feature for Azure Database for MySQL - Flexible Server.
+title: Accelerated logs feature
+description: This article describes the accelerated logs feature in Azure Database for MySQL - Flexible Server and its benefits for high-performance workloads.
 author: code-sidd
 ms.author: sisawant
 ms.reviewer: maghan
-ms.date: 11/07/2023
+ms.date: 05/21/2024
 ms.service: mysql
 ms.subservice: flexible-server
-ms.topic: conceptual
+ms.topic: concept-article
 ms.custom:
-  - references_regions
-  - ignite-2023
+    - references_regions
+    - ignite-2023
+#customer intent: As a reader, I want to understand the concept of accelerated logs in Azure Database for MySQL - Flexible Server.
 ---
 
-# Accelerated logs feature in Azure Database for MySQL - Flexible Server (Preview)
+# Accelerated logs feature in Azure Database for MySQL - Flexible Server
 
 [!INCLUDE [applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
-This article outlines the accelerated logs feature during its preview phase. It guides you on how to enable or disable this feature for Azure Database for MySQL flexible server based on the Business Critical service tier.
+This article outlines the accelerated logs feature and guides you through enabling or disabling this feature for the Azure Database for MySQL service based on the Business Critical service tier.
 
 > [!IMPORTANT]  
-> The accelerated logs feature is currently in preview and subject to [limitations](#limitations) and ongoing development. This feature is only available for servers based on the Business -Critical service tier. We recommend using it in non-production environments, such as development, testing, or quality assurance, to evaluate its performance and suitability for your specific use cases.
+> The accelerated logs feature is currently in and subject to [limitations](#limitations) and ongoing development. This feature is only available for servers based on the Business -Critical service tier. We recommend using it in non-production environments, such as development, testing, or quality assurance, to evaluate its performance and suitability for your specific use cases.
 
 ## Introduction
 
-The accelerated logs feature is designed to provide a significant performance boost for users of the Business Critical service tier in Azure Database for MySQL flexible server. It substantially enhances performance by optimizing transactional log-related operations. Enabling this feature allows a server to automatically store transactional logs on faster storage to enhance server throughput without incurring any extra cost.
+The accelerated logs feature is designed to significantly boost performance for users of the Business Critical service tier in Azure Database for MySQL flexible server. It substantially enhances performance by optimizing transactional log-related operations. Enabling this feature allows a server to automatically store transactional logs on faster storage to enhance server throughput without incurring any extra cost.
 
-Database servers with mission-critical workloads demand robust performance, requiring high throughput and substantial IOPS. However, these databases can also be sensitive to latency fluctuations in server transaction commit times. The accelerated logs feature is designed to address these challenges by optimizing the placement of transactional logs on high-performance storage. By separating transaction log operations from database queries and data updates, a significant improvement is achieved in database transaction commit latency times.
+Database servers with mission-critical workloads demand robust performance, requiring high throughput, and substantial IOPS. However, these databases can also be sensitive to latency fluctuations in server transaction commit times. The accelerated logs feature is designed to address these challenges by optimizing the placement of transactional logs on high-performance storage. Separating transaction log operations from database queries and data updates results in significant improvement in database transaction commit latency times.
 
 ### Key benefits
 
 - **Enhanced throughput:** Experience up to 2x increased query throughput in high concurrency scenarios, resulting in faster query execution. This improvement also comes with reduced latency, reducing latency by up to 50%, for enhanced performance.
 - **Cost efficiency**: Accelerated logs provide enhanced performance at no extra expense, offering a cost-effective solution for mission-critical workloads.
-- **Enhanced scalability:** Accelerated logs can accommodate growing workloads, making it an ideal choice for applications that need to scale easily while maintaining high performance. Applications and services on the Business Critical service tier benefit from more responsive interactions and reduced query wait times.
+- **Enhanced scalability:** Accelerated logs can accommodate growing workloads, making them ideal for applications that need to scale easily while maintaining high performance. Applications and services on the Business Critical service tier benefit from more responsive interactions and reduced query wait times.
 
-## Limitations
-
-- During the preview phase,  you can't enable the accelerated logs feature on servers that have the following features enabled.
-    - [High Availability](./concepts-high-availability.md) (HA) servers.
-    - Primary servers with [Read Replica](./concepts-read-replicas.md) servers created. 
-    - Servers enabled with [Customer Managed Keys](./concepts-customer-managed-key.md)  (CMK).
-
-- Accelerated logs feature in preview is currently available only in specific regions. [Learn more about supported regions](#the-accelerated-logs-feature-is-available-in-the-following-regions).
-
-- After the accelerated logs feature is activated, any previously configured value for the ["binlog_expire_seconds"](https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_binlog_expire_logs_seconds) server parameter will be disregarded and not considered.
+## Regions
 
-
-## The accelerated logs feature is available in the following regions
+The accelerated logs feature is available in the following regions.
 
 - Australia East
 - Canada Central
@@ -72,32 +63,32 @@ Database servers with mission-critical workloads demand robust performance, requ
 - West US 2
 - West US 3
 
-## Enable accelerated logs feature (preview)
+## Enable accelerated logs feature
 
-The enable accelerated logs feature is available during the preview phase. You can enable this feature during server creation or on an existing server. The following sections provide details on how to enable the accelerated logs feature.
+The enable accelerated logs feature is available during the phase. You can enable this feature during server creation or on an existing server. The following sections provide details on how to enable the accelerated logs feature.
 
 ### Enable accelerated logs during server creation
 
 This section provides details specifically for enabling the accelerated logs feature. You can follow these steps to enable Accelerated logs while creating your flexible server.
 
 > [!IMPORTANT]  
-> The accelerated logs feature is only available for servers based on the Business Critical service tier. It is recommended to disable the feature when scaling down to any other service tier.
+> The accelerated logs feature is only available for servers based on the Business Critical service tier. Disabling the feature when scaling down to any other service tier is recommended.
 
-1. In the [Azure portal](https://portal.azure.com/), choose flexible Server and Select **Create**.  For details on how to fill details such as **Subscription**, **Resource group**, **Server name**, **Region**, and other fields, see [how-to documentation](./quickstart-create-server-portal.md) for the server creation.
+1. In the [Azure portal](https://portal.azure.com/), choose flexible Server and Select **Create**. For details on how to fill details such as **Subscription**, **Resource group**, **Server name**, **Region**, and other fields, see [how-to documentation](quickstart-create-server-portal.md) for the server creation.
 
 1. Select the **Configure server** option to change the default compute and storage.
 
-1. The checkbox for **Accelerated logs** under the Storage option is visible only when the server from the **Business Critical** compute tier is selected.
+1. The checkbox for Accelerated logs under the Storage option is visible only when the server from the Business Critical compute tier is selected.
 
-    :::image type="content" source="./media/concepts-accelerated-logs/accelerated-logs-mysql-portal-create.png" alt-text="Screenshot shows accelerated logs during server create." lightbox="./media/concepts-accelerated-logs/accelerated-logs-mysql-portal-create.png":::
+    :::image type="content" source="media/concepts-accelerated-logs/accelerated-logs-mysql-portal-create.png" alt-text="Screenshot shows accelerated logs during server create." lightbox="media/concepts-accelerated-logs/accelerated-logs-mysql-portal-create.png":::
 
-1. Enable the checkbox for **Accelerated logs** to enable the feature. If the high availability option is checked, the accelerated logs feature isn't available to choose. Learn more about [limitations](#limitations) during preview.
+1. Enable the checkbox for **Accelerated logs** to enable the feature. If the high availability option is checked, the accelerated logs feature isn't available to choose. To learn more, visit [limitations](#limitations).
 
-1. Select the **Compute size** from the dropdown list. Select **Save** and proceed to deploy your Azure Database for MySQL flexible server instance following instructions from [how-to create a server](./quickstart-create-server-portal.md).
+1. Select the **Compute size** from the dropdown list. Select **Save** and deploy your Azure Database for MySQL flexible server instance following instructions from [how-to create a server](quickstart-create-server-portal.md).
 
 ### Enable accelerated logs on your existing server
 
-During the Public Preview phase, this section details enabling accelerated logs. You can follow these steps to enable accelerated logs on your Azure Database for MySQL flexible server instance.
+During the Public phase, this section details enabling accelerated logs. You can follow these steps to enable accelerated logs on your Azure Database for MySQL flexible server instance.
 
 > [!NOTE]  
 > Your server will restart during the deployment process, so ensure you either pause your workload or schedule it during a time that aligns with your application maintenance or off-hours.
@@ -106,13 +97,13 @@ During the Public Preview phase, this section details enabling accelerated logs.
 
 1. Under the Settings sections, navigate to the **Compute + Storage** page. You can enable **Accelerated Logs** by selecting the checkbox under the **Storage** section.
 
-    :::image type="content" source="./media/concepts-accelerated-logs/accelerated-logs-mysql-portal-enable.png" alt-text="Screenshot shows accelerated logs enable after server create." lightbox="./media/concepts-accelerated-logs/accelerated-logs-mysql-portal-enable.png":::
+    :::image type="content" source="media/concepts-accelerated-logs/accelerated-logs-mysql-portal-enable.png" alt-text="Screenshot shows accelerated logs enable after server create." lightbox="media/concepts-accelerated-logs/accelerated-logs-mysql-portal-enable.png":::
 
-1. Select **Save** and wait for the deployment process to be completed. Once you receive a successful deployment message, the feature is ready to be used.
+1. Select **Save** and wait for the deployment process to be completed. The feature is ready to be used once you receive a successful deployment message.
 
-## Disable accelerated logs feature (preview)
+## Disable the accelerated logs feature
 
-During the public preview phase, disabling the  accelerated logs feature is a straightforward process:
+During the public phase, disabling the accelerated logs feature is a straightforward process:
 
 > [!NOTE]  
 > Your server will restart during the deployment process, so ensure you either pause your workload or schedule it during a time that aligns with your application maintenance or off-hours.
@@ -121,11 +112,34 @@ During the public preview phase, disabling the  accelerated logs feature is a st
 
 1. Under the Settings sections, navigate to the **Compute + Storage** page. You find the "Accelerated Logs" checkbox under the Storage section. Uncheck this box to disable the feature.
 
-    :::image type="content" source="./media/concepts-accelerated-logs/accelerated-logs-mysql-portal-disable.png" alt-text="Screenshot shows accelerated logs disable after server create." lightbox="./media/concepts-accelerated-logs/accelerated-logs-mysql-portal-disable.png":::
+    :::image type="content" source="media/concepts-accelerated-logs/accelerated-logs-mysql-portal-disable.png" alt-text="Screenshot shows accelerated logs disable after server create." lightbox="media/concepts-accelerated-logs/accelerated-logs-mysql-portal-disable.png":::
 
 1. Select **Save** and wait for the deployment process to be completed. After you receive a successful deployment message, the feature is disabled.
 
+## Limitations
+
+The accelerated logs feature in Azure Database for MySQL - Flexible Server has the following limitations:
+
+- During the phase, you can't enable the accelerated logs feature on servers that have the following features enabled:
+    - [High availability concepts in Azure Database for MySQL - Flexible Server](concepts-high-availability.md) (HA) servers.
+    - Created primary servers with [Read replicas in Azure Database for MySQL - Flexible Server](concepts-read-replicas.md) servers.
+    - Servers enabled with [Data encryption with customer managed keys for Azure Database for MySQL - Flexible Server](concepts-customer-managed-key.md) (CMK).
+
+- The accelerated logs feature is currently available only in specific [regions](#regions).
+
+- After the accelerated logs feature is activated, any previously configured value for the ["binlog_expire_seconds"](https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_binlog_expire_logs_seconds) server parameter will be disregarded and not considered.
+
+- The accelerated logs feature is subject to ongoing development and might have other limitations or changes in future releases.
+
+- During the phase, you can't enable the accelerated logs feature on servers with the following features.
+    - [High availability concepts in Azure Database for MySQL - Flexible Server](concepts-high-availability.md) (HA) servers.
+    - Created primary servers with [Read replicas in Azure Database for MySQL - Flexible Server](concepts-read-replicas.md) servers.
+    - Servers enabled with [Data encryption with customer managed keys for Azure Database for MySQL - Flexible Server](concepts-customer-managed-key.md) (CMK).
+
+- Accelerated logs feature is currently available only in specific [regions](#regions).
+- After the accelerated logs feature is activated, any previously configured value for the ["binlog_expire_seconds"](https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_binlog_expire_logs_seconds) server parameter will be disregarded and not considered.
+
 ## Related content
 
-- [Create an Azure Database for MySQL flexible server instance in the portal](quickstart-create-server-portal.md)
-- [Service limitations](concepts-limitations.md)
+- [Create an Azure Database for MySQL flexible server by using the Azure portal](quickstart-create-server-portal.md)
+- [Limitations in Azure Database for MySQL](concepts-limitations.md)