Merge pull request #281405 from xboxeer/main

August Release Notes

Author: ttorble

articles/mysql/TOC.yml

@@ -36,6 +36,8 @@
             href: flexible-server/release-notes/may-2024.md
           - name: June 2024
             href: flexible-server/release-notes/june-2024.md
+          - name: August 2024
+            href: flexible-server/release-notes/august-2024.md
       - name: Service tiers
         href: flexible-server/concepts-service-tiers-storage.md
   - name: Quickstarts

articles/mysql/concepts-version-policy.md

@@ -28,7 +28,7 @@ Azure Database for MySQL currently supports the following major and minor versio
 | Version | [Single Server](single-server/overview.md)<br />Current minor version | [Flexible Server](flexible-server/overview.md)<br />Current minor version |
 | :--- | :--- | :--- |
 | MySQL Version 5.7 | [5.7.32](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-29.html) | [5.7.44](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html) |
-| MySQL Version 8.0 | [8.0.15](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-15.html) | [8.0.36](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-36.html) |
+| MySQL Version 8.0 | [8.0.15](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-15.html) | [8.0.37](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-37.html) |
 
 > [!NOTE]  
 > In the Single Server deployment option, a gateway redirects the connections to server instances. After the connection is established, the MySQL client displays the version of MySQL set in the gateway, not the actual version running on your MySQL server instance. To determine the version of your MySQL server instance, use the `SELECT VERSION();` command at the MySQL prompt. If your application has a requirement to connect to a specific major version, say v5.7 or v8.0, you can do so by changing the port in your server connection string as explained in our documentation [here.](concepts-supported-versions.md#connect-to-a-gateway-node-that-is-running-a-specific-mysql-version)
@@ -54,7 +54,7 @@ The retirement details for MySQL major versions are listed in the following tabl
 
 ## What will happen to Azure Database for MySQL service after MySQL community version is retired in October 2023?
 
-In line with Oracle's announcement regarding the end-of-life (EOL) of [MySQL Community Version v5.7 in __October 2023__](https://www.oracle.com/us/support/library/lsp-tech-chart-069290.pdf) (Page 23), we at Azure are actively preparing for this important transition. This development specifically impacts customers who are currently utilizing Version 5.7 of Azure Database for MySQL - Single Server and Flexible Server.
+In line with Oracle's announcement regarding the end-of-life of [MySQL Community Version v5.7 in __October 2023__](https://www.oracle.com/us/support/library/lsp-tech-chart-069290.pdf) (Page 23), we at Azure are actively preparing for this important transition. This development specifically impacts customers who are currently utilizing Version 5.7 of Azure Database for MySQL - Single Server and Flexible Server.
 
 In response to the customer's requests, Microsoft decided to prolong the support for Azure Database for MySQL beyond __October 2023__. During the extended support period, which lasts until __September 2025__, Microsoft prioritizes the availability, reliability, and security of the service. While there are no specific guarantees regarding minor version upgrades, we implement essential modifications to ensure that the service remains accessible, dependable, and protected. Our plan includes:
 

articles/mysql/flexible-server/release-notes/august-2024.md

@@ -0,0 +1,30 @@
+---
+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.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. 
+
+## Engine version changes
+Existing engine version >=8.0.34 server upgrades to 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.
+
+## 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
+- 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