Merge pull request #284202 from markingmyname/281405

denrea · web-flow · commit 6b22970365bf · 2024-08-09T10:52:41.000-07:00
[MySQL] Edit August release notes
diff --git a/articles/mysql/concepts-version-policy.md b/articles/mysql/concepts-version-policy.md
diff --git a/articles/mysql/flexible-server/release-notes/april-2024.md b/articles/mysql/flexible-server/release-notes/april-2024.md
@@ -4,36 +4,41 @@ description: Learn about the release notes for Azure Database for MySQL Flexible
 author: xboxeer
 ms.author: yuzheng1
 ms.reviewer: maghan
-ms.date: 06/18/2024
+ms.date: 08/09/2024
 ms.service: azure-database-mysql
 ms.subservice: flexible-server
 ms.topic: conceptual
 ---
 
-# Azure Database For MySQL Flexible Server April 2024 Maintenance
+# Azure Database For MySQL - Flexible Server April 2024 maintenance
 
 We're pleased to announce the April 2024 maintenance for Azure Database for MySQL Flexible Server. This maintenance incorporates several new features and improvement, along with known issue fix, minor version upgrade, and security patches.
 
-> [!NOTE]
+> [!NOTE]  
 > We regret to inform our users that after a thorough assessment of our current maintenance processes, we have observed an unusually high failure rate across the board. Consequently, we have made the difficult decision to cancel the minor version upgrade maintenance scheduled for April. The rescheduling of the next minor version upgrade maintenance remains undetermined at this time. We commit to providing at least one month's notice prior to the rescheduled maintenance to ensure all users are adequately prepared.
-> 
-> Please notes that if your maintenance has already been completed, whether it was rescheduled to an earlier date or carried out as initially scheduled, and concluded successfully, your services are not affected by this cancellation. Your maintenance is considered successful and will not be impacted by the current round of cancellations.
+>  
+> Notes that if your maintenance has already been completed, whether it was rescheduled to an earlier date or carried out as initially scheduled, and concluded successfully, your services are not affected by this cancellation. Your maintenance is considered successful and will not be affected by the current round of cancellations.
 
 ## Engine version changes
+
 All existing engine version server upgrades to 8.0.36 engine version.
 
 To check your engine version, run `SELECT VERSION();` command at the MySQL prompt
 
 ## Features
-### [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-databases-introduction) 
+
+### [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-databases-introduction)
+
 - Introducing Defender for Cloud support to simplify security management with threat protection from anomalous database activities in Azure Database for MySQL flexible server instances.
-  
+
 ## Improvement
+
 - Expose old_alter_table for 8.0.x.
 
-## Known Issues Fix
+## Known issues fixes
+
 - Fixed the issue where `GTID RESET` operation's retry interval was excessively long.
 - Fixed the issue that data-in HA failover stuck because of system table corrupt
-- Fixed the issue that in point-in-time restore that database or table starts with special keywords may be ignored
+- Fixed the issue that in point-in-time restore that database or table starts with special keywords might be ignored
 - Fixed the issue where, if there's replication failure, the system now ignores the replication latency metric instead of displaying a '0' latency value.
 - Fixed the issue where under certain circumstances MySQL RP does not correctly get notified of a "private dns zone move operation". The issue will cause the server to be showing incorrect ARM resource ID of the associated private dns zone resource.
diff --git a/articles/mysql/flexible-server/release-notes/august-2024.md b/articles/mysql/flexible-server/release-notes/august-2024.md
@@ -1,30 +1,36 @@
 ---
-title: Release notes for Azure Database for MySQL Flexible Server - August 2024
+title: Release notes for Azure Database for MySQL - Flexible Server - August 2024
 description: Learn about the release notes for Azure Database for MySQL Flexible Server August 2024.
 author: xboxeer
 ms.author: yuzheng1
-ms.date: 08/01/2024
+ms.reviewer: maghan
+ms.date: 08/09/2024
 ms.service: azure-database-mysql
 ms.subservice: flexible-server
 ms.topic: conceptual
 ---
 
-# Azure Database For MySQL Flexible Server August 2024 Maintenance
-We're pleased to announce the June 2024 maintenance for Azure Database for MySQL Flexible Server. This maintenance updates all existing 8.0.34 and afterwards engine version servers to 8.0.37 engine version, along with several security improvements, known issue fixes. 
+# Azure Database For MySQL - Flexible Server August 2024 maintenance
+
+We're pleased to announce the June 2024 maintenance of the Azure Database for MySQL Flexible Server. This maintenance updates all existing 8.0.34 and, after, engine version servers to the 8.0.37 engine version, along with several security improvements and known issue fixes.
 
 ## Engine version changes
-Existing engine version >=8.0.34 server upgrades to 8.0.37 engine version.
+
+The existing engine version is >=8.0.34, and the server upgrades to the 8.0.37 engine version.
 To check your engine version, run `SELECT VERSION();` command at the MySQL prompt
 
-> [!NOTE]
-> Percona has identified a [critical bug](https://www.percona.com/blog/do-not-upgrade-to-any-version-of-mysql-after-8-0-37/?utm_campaign=2024-blog-q3&utm_content=300046226&utm_medium=social&utm_source=linkedin&hss_channel=lcp-421929) in MySQL versions 8.0.38, 8.4.1, and 9.0.0 that causes the MySQL daemon to crash upon restart if over 10,000 tables exist. Azure MySQL will not upgrade to the buggy MySQL versions 8.0.38, 8.4.1, and 9.0.0 in the August maintenance. Instead, we will skip these versions and upgrade directly to a future MySQL engine version that has resolved this issue. Microsoft Azure MySQL remains committed to providing our customers with the most secure and stable PaaS database service.
+> [!NOTE]  
+> Percona has identified a [critical bug](https://www.percona.com/blog/do-not-upgrade-to-any-version-of-mysql-after-8-0-37/?utm_campaign=2024-blog-q3&utm_content=300046226&utm_medium=social&utm_source=linkedin&hss_channel=lcp-421929) in MySQL versions 8.0.38, 8.4.1, and 9.0.0 that causes the MySQL daemon to crash upon restart if over 10,000 tables exist. Azure MySQL will not upgrade to the buggy MySQL versions 8.0.38, 8.4.1, and 9.0.0 in the August maintenance. Instead, we will skip these versions and upgrade directly to a future MySQL engine version that has resolved this issue. Microsoft Azure MySQL remains committed to providing customers with the most secure and stable PaaS database service.
 
 ## Features
+
 No new features are being introduced in this maintenance update.
 
 ## Improvement
+
 - Many security improvements have been made to the service during this maintenance.
-    
-## Known Issues Fix
+
+## Known issues fixes
+
 - Fix the issue that for some servers migrated from single server to flexible server, execute table partition leads to table corrupted
-- Fix the issue that for some servers with audit/slow log enabled, when large number of logs is generated, these servers might be missing server metrics and start operation might be stuck for these servers if they are in stopped state
+- Fix the issue that for some servers with audit/slow log enabled, when a large number of logs are generated, these servers might be missing server metrics, and start operation might be stuck for these servers if they are in a stopped state.
diff --git a/articles/mysql/flexible-server/release-notes/february-2024.md b/articles/mysql/flexible-server/release-notes/february-2024.md
@@ -4,32 +4,36 @@ description: Learn about the release notes for Azure Database for MySQL Flexible
 author: xboxeer
 ms.author: yuzheng1
 ms.reviewer: maghan
-ms.date: 06/18/2024
+ms.date: 08/09/2024
 ms.service: azure-database-mysql
 ms.subservice: flexible-server
 ms.topic: conceptual
 ---
 
-# Azure Database For MySQL Flexible Server February 2024 Maintenance
+# Azure Database For MySQL - Flexible Server February 2024 maintenance
 
 We're pleased to announce the February 2024 maintenance for Azure Database for MySQL Flexible Server. This maintenance mainly focuses on known issue fix, underlying OS upgrading and vulnerability patching.
 
-> [!NOTE]
-> During the preliminary stages of our February-March maintenance period, we identified a regression issue that necessitated a reevaluation of our scheduled maintenance activities. Consequently, all maintenance sessions originally planned for the period from March 2nd, 13:00 UTC, to March 14th, 00:00 UTC, have been canceled. We are currently in the process of rescheduling these maintenance activities. Affected customers will be promptly notified of the new maintenance timetable. We apologize for any inconvenience this may cause and thank you for your understanding and continued support.
+> [!NOTE]  
+> During the preliminary stages of our February-March maintenance period, we identified a regression issue that necessitated a reevaluation of our scheduled maintenance activities. Consequently, all maintenance sessions originally planned for the period from March 2nd, 13:00 UTC, to March 14th, 00:00 UTC, have been canceled. We are currently in the process of rescheduling these maintenance activities. Affected customers will be promptly notified of the new maintenance timetable. We apologize for any inconvenience this might cause and thank you for your understanding and continued support.
 
 ## Engine version changes
- - All existing 5.7.42 engine version server will upgrade to 5.7.44 engine version.
- - All existing 8.0.34 engine version server will upgrade to 8.0.35 engine version.
+
+- All existing 5.7.42 engine version server will upgrade to 5.7.44 engine version.
+- All existing 8.0.34 engine version server will upgrade to 8.0.35 engine version.
 
 To check your engine version, run `SELECT VERSION();` command at the MySQL prompt
 
 ## Features
+
 There will be no new features in this maintenance update.
 
 ## Improvement
+
 There will be no new improvement in this maintenance update.
 
-## Known Issues Fix
+## Known issues fixes
+
 - Fix HA standby replication dead lock issue caused by slave_preserve_commit_order.
 - Fix promotion stuck issue when source server is unavailable or source region is down. Improve customer experience on replica promotion to better support disaster recovery.
 - Fix the default value of character_set_server & collation_server.
diff --git a/articles/mysql/flexible-server/release-notes/january-2024.md b/articles/mysql/flexible-server/release-notes/january-2024.md
@@ -4,32 +4,40 @@ description: Learn about the release notes for Azure Database for MySQL Flexible
 author: xboxeer
 ms.author: yuzheng1
 ms.reviewer: maghan
-ms.date: 06/18/2024
+ms.date: 08/09/2024
 ms.service: azure-database-mysql
 ms.subservice: flexible-server
 ms.topic: conceptual
 ---
 
-# Azure Database For MySQL Flexible Server January 2024 Maintenance
+# Azure Database For MySQL - Flexible Server January 2024 maintenance
 
 We are pleased to announce the January 2024 maintenance for Azure Database for MySQL Flexible Server. This maintenance incorporates several new features and resolves known issues for enhanced performance and reliability.
-> [!NOTE]
-> Between 2024/1/12 04:00 UTC and 2024/1/15 07:00 UTC, we strategically paused Azure MySQL maintenance to proactively address a detected issue that could lead to maintenance interruptions. We're happy to report that maintenance operations are fully restored. For those impacted, you're welcome to utilize our flexible maintenance feature to conveniently reschedule your maintenance times as needed.
+> [!NOTE]  
+> Between 2024/1/12 04:00 UTC and 2024/1/15 07:00 UTC, we strategically paused Azure MySQL maintenance to proactively address a detected issue that could lead to maintenance interruptions. We're happy to report that maintenance operations are fully restored. For those affected, you're welcome to utilize our flexible maintenance feature to conveniently reschedule your maintenance times as needed.
 
 ## Engine version changes
+
 There will be no engine version changes in this maintenance update.
 
 ## Features
+
 ### [Accelerated Logs V2](../concepts-accelerated-logs.md)
+
 - Introducing a new type of disk designed to offer superior performance in storing binary logs and redo logs.
 
 ## Improvement
 
 ### [Audit Log Improvement](../concepts-audit-logs.md)
+
 - In alignment with our users' expectations for the audit log, we have introduced wildcard support for audit log usernames and added connection status for connection logs.
 
-## Known Issues Fix
+## Known issues fixes
+
 ### Support Data-in Replication in Major Version Upgrade
+
 - During an upgrade from 5.7 to 8.0, data-in replication encounters issues due to a known bug in the MySQL community. With this January 2024 maintenance, we have addressed this concern, enabling data-in replication support for servers upgraded from version 5.7.
+
 ### Server Operations Blockage After Moving Subscription or Resource Group
+
 - Several server operations were hindered post the transfer of subscription or resource group owing to incomplete server information updates. This issue has been resolved in this January 2024 maintenance, ensuring unhindered movement of subscriptions and resource groups.
diff --git a/articles/mysql/flexible-server/release-notes/june-2024.md b/articles/mysql/flexible-server/release-notes/june-2024.md
@@ -4,29 +4,33 @@ description: Learn about the release notes for Azure Database for MySQL Flexible
 author: xboxeer
 ms.author: yuzheng1
 ms.reviewer: maghan
-ms.date: 06/18/2024
+ms.date: 08/09/2024
 ms.service: azure-database-mysql
 ms.subservice: flexible-server
 ms.topic: conceptual
 ---
 
-# Azure Database For MySQL Flexible Server June 2024 Maintenance
+# Azure Database For MySQL - Flexible Server June 2024 maintenance
 
-We're pleased to announce the June 2024 maintenance for Azure Database for MySQL Flexible Server. In this maintenance update, we're addressing some availability issues that have been impacting a subset of our servers. While most servers remain unaffected, a small portion experiences maintenance activities to enhance their performance and stability. We appreciate your understanding and patience as we work to improve our service.
+We're pleased to announce the June 2024 maintenance for Azure Database for MySQL Flexible Server. In this maintenance update, we're addressing some availability issues that have been affecting a subset of our servers. While most servers remain unaffected, a small portion experiences maintenance activities to enhance their performance and stability. We appreciate your understanding and patience as we work to improve our service.
 
 ## Engine version changes
+
 No engine version upgrade in this maintenance
 
 To check your engine version, run `SELECT VERSION();` command at the MySQL prompt
 
 ## Features
+
 No new features are being introduced in this maintenance update.
 
 ## Improvement
+
 - Allow customers to truncate performance_schema tables by invoking a predefined stored procedure.
 - Improve the startup time for servers with large amount of tablespaces.
-    
-## Known Issues Fix
-- Fixed the issue that MySQL engine may not receive the shutdown signal during scaling and maintenance, which may lead to long recovery time.
-- Fixed the issue that if server with originalPrimaryName is deleted due to HA failover->disable HA action, earlier ATP update operation failed. 
+
+## Known issues fixes
+
+- Fixed the issue that MySQL engine might not receive the shutdown signal during scaling and maintenance, which might lead to long recovery time.
+- Fixed the issue that if server with originalPrimaryName is deleted due to HA failover->disable HA action, earlier ATP update operation failed.
 - Fixed the issue that unhealthy servers/Burstable servers without credits will now throw ServerNotSucceeded instead of Internal Server Error
diff --git a/articles/mysql/flexible-server/release-notes/may-2024.md b/articles/mysql/flexible-server/release-notes/may-2024.md
@@ -4,31 +4,35 @@ description: Learn about the release notes for Azure Database for MySQL Flexible
 author: xboxeer
 ms.author: yuzheng1
 ms.reviewer: maghan
-ms.date: 06/18/2024
+ms.date: 08/09/2024
 ms.service: azure-database-mysql
 ms.subservice: flexible-server
 ms.topic: conceptual
 ---
 
-# Azure Database For MySQL Flexible Server May 2024 Maintenance
+# Azure Database For MySQL - Flexible Server May 2024 maintenance
 
 We're pleased to announce the May 2024 maintenance for Azure Database for MySQL Flexible Server. This maintenance incorporates several new features and improvement, along with known issue fix, and security patches.
 
 ## Engine version changes
+
 No engine version upgrade in this maintenance
 
 To check your engine version, run `SELECT VERSION();` command at the MySQL prompt
 
 ## Features
+
 ### [Generally Available of Accelerated Logs in Azure Database for MySQL Flexible Server](../concepts-accelerated-logs.md)
-- This feature is available within the Business-Critical service tier, which significantly enhances the performance of Azure Database for MySQL Flexible Server instances. It offers a dynamic solution designed for high throughput needs, reducing latency with no additional cost. 
+
+- This feature is available within the Business-Critical service tier, which significantly enhances the performance of Azure Database for MySQL Flexible Server instances. It offers a dynamic solution designed for high throughput needs, reducing latency with no additional cost.
 
 ## Improvement
+
 - Improved server restart logic, server restart has a timeout of 2 hours for none burstable servers, 4 hours timeout for burstable servers. After server restart workflow timeout, it would roll back and set the server state to Succeeded.
 - Improved the data-in replication procedures to show the real error message and safe exit when exception happens.
-- Improved the read replica creation workflow to precheck the VNet setting.
-    
-## Known Issues Fix
+- Read replica improvement for the creation workflow to precheck the virtual network setting.
+
+## Known issues fixes
+
 - Fixed the issue that the server parameter max_connections and table_open_cache can't be configured correctly
 - Fixed the issue where executing `CREATE AADUSER IF NOT EXISTS 'myuser' IDENTIFIED BY 'CLIENT_ID'` when the user already exists incorrectly set the binlog record, affecting replica and high availability functionalities.
-
