Merge pull request #201978 from markingmyname/mysqlsupport

[MySQL] Version policy article and service tiers article

Author: Stacyrch140

articles/mysql/.openpublishing.redirection.mysql.json

@@ -276,8 +276,8 @@
         "redirect_document_id": false
     },
     {
-        "source_path_from_root": "/articles/mysql/concepts-version-policy.md",
-        "redirect_url": "/azure/mysql/single-server/concepts-version-policy",
+        "source_path_from_root": "/articles/mysql/single-server/concepts-version-policy.md",
+        "redirect_url": "/azure/mysql/concepts-version-policy",
         "redirect_document_id": false
     },
     {
@@ -735,5 +735,15 @@
         "redirect_url": "/azure/mysql/single-server/tutorial-design-database-using-powershell",
         "redirect_document_id": false
     },
-    ]
+    {
+        "source_path_from_root": "/articles/mysql/single-server/concepts-supported-versions.md",
+        "redirect_url": "/azure/mysql/single-server/concepts-connect-to-a-gateway-node",
+        "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/mysql/flexible-server/concepts-compute-storage.md",
+        "redirect_url": "/azure/mysql/flexible-server/concepts-service-tiers-storage",
+        "redirect_document_id": true
+    }
+  ]
 }

articles/mysql/TOC.yml

@@ -16,7 +16,7 @@
   - name: Prepay for reserved capacity
     href: single-server/concept-reserved-pricing.md
   - name: Version support policy
-    href: single-server/concepts-version-policy.md
+    href: concepts-version-policy.md
     displayName: version policy
 - name: Flexible Server
   items:
@@ -274,8 +274,6 @@
     items:
     - name: What is Single Server?
       href: single-server/single-server-overview.md
-    - name: Supported versions
-      href: single-server/concepts-supported-versions.md
     - name: Pricing Tiers
       items:
       - name: Pricing tiers

articles/mysql/single-server/concepts-version-policy.md renamed to articles/mysql/concepts-version-policy.md

@@ -1,17 +1,18 @@
 ---
-title: Version support policy - Azure Database for MySQL - Single Server and Flexible Server (Preview)
+title: Version support policy - Azure Database for MySQL - Single Server and Flexible Server
 description: Describes the policy around MySQL major and minor versions in Azure Database for MySQL
 author: sr-msft
 ms.author: srranga
 ms.service: mysql
 ms.subservice: single-server
 ms.topic: conceptual
 ms.custom: fasttrack-edit
-ms.date: 11/03/2020
+ms.date: 06/21/2022
 ---
+
 # Azure Database for MySQL version support policy
 
-[!INCLUDE[applies-to-mysql-single-flexible-server](../includes/applies-to-mysql-single-flexible-server.md)]
+[!INCLUDE [applies-to-mysql-single-flexible-server](includes/applies-to-mysql-single-flexible-server.md)]
 
 This page describes the Azure Database for MySQL versioning policy, and is applicable to Azure Database for MySQL - Single Server and Azure Database for MySQL - Flexible Server (Preview) deployment modes.
 
@@ -21,9 +22,9 @@ Azure Database for MySQL has been developed from [MySQL Community Edition](https
 
 Azure Database for MySQL currently supports the following major and minor versions of MySQL:
 
-| Version | [Single Server](overview.md) <br/> Current minor version |[Flexible Server](../flexible-server/overview.md) <br/> Current minor version  |
+| Version | [Single Server](single-server/overview.md) <br/> Current minor version |[Flexible Server](flexible-server/overview.md) <br/> Current minor version  |
 |:-------------------|:-------------------------------------------|:---------------------------------------------|
-|MySQL Version 5.6 |  [5.6.47](https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-47.html)(Retired) | Not supported|
+|MySQL Version 5.6 | [5.6.47](https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-47.html)(Retired) | Not supported|
 |MySQL Version 5.7 | [5.7.29](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-29.html) | [5.7.37](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-37.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.28](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html)|
 
@@ -48,7 +49,7 @@ Azure Database for MySQL automatically performs minor version upgrades to the Az
 The table below provides the retirement details for MySQL major versions. The dates follow the [MySQL versioning policy](https://www.mysql.com/support/eol-notice.html).
 
 | Version | What's New | Azure support start date | Retirement date|
-| ----- | ----- | ------ | ----- |
+| ------- | ---------- | ------------------------ | -------------- |
 | [MySQL 5.6](https://dev.mysql.com/doc/relnotes/mysql/5.6/en/)| [Features](https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-49.html)  | March 20, 2018 | February 2021
 | [MySQL 5.7](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-31.html) | March 20, 2018 | October 2023
 | [MySQL 8](https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-21.html)) | December 11, 2019 | April 2026
@@ -66,6 +67,4 @@ After the retirement date for each MySQL database version, if you continue runni
 
 ## Next steps
 
-- See Azure Database for MySQL - Single Server [supported versions](./concepts-supported-versions.md)
-- See Azure Database for MySQL - Flexible Server [supported versions](../flexible-server/concepts-supported-versions.md)
 - See MySQL [dump and restore](./concepts-migrate-dump-restore.md) to perform upgrades.

articles/mysql/flexible-server/concepts-compute-storage.md renamed to articles/mysql/flexible-server/concepts-service-tiers-storage.md

@@ -1,5 +1,5 @@
 ---
-title: Compute and storage options - Azure Database for MySQL - Flexible Server
+title: Azure Database for MySQL - Flexible Server service tiers
 description: This article describes the compute and storage options in Azure Database for MySQL - Flexible Server.
 author: Bashar-MSFT
 ms.author: bahusse
@@ -10,12 +10,11 @@ ms.topic: conceptual
 ms.date: 05/24/2022
 ---
 
-# Compute and storage options in Azure Database for MySQL - Flexible Server
+# Azure Database for MySQL - Flexible Server service tiers
 
 [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
-
-You can create an Azure Database for MySQL Flexible Server in one of three different compute tiers: Burstable, General Purpose, and Business Critical. The compute tiers are differentiated by the underlying VM SKU used B-series, D-series, and E-series. The choice of compute tier and size determines the memory and vCores available on the server. The same storage technology is used across all compute tiers. All resources are provisioned at the MySQL server level. A server can have one or many databases.
+You can create an Azure Database for MySQL Flexible Server in one of three different service tiers: Burstable, General Purpose, and Business Critical. The service tiers are differentiated by the underlying VM SKU used B-series, D-series, and E-series. The choice of compute tier and size determines the memory and vCores available on the server. The same storage technology is used across all service tiers. All resources are provisioned at the MySQL server level. A server can have one or many databases.
 
 | Resource / Tier | **Burstable** | **General Purpose** | **Business Critical** |
 |:---|:----------|:--------------------|:---------------------|
@@ -39,7 +38,7 @@ To choose a compute tier, use the following table as a starting point.
 
 After you create a server, the compute tier, compute size, and storage size can be changed. Compute scaling requires a restart and takes between 60-120 seconds, while storage scaling does not require restart. You also can independently adjust the backup retention period up or down. For more information, see the [Scale resources](#scale-resources) section.
 
-## Compute tiers, size, and server types
+## Service tiers, size, and server types
 
 Compute resources can be selected based on the tier and size. This determines the vCores and memory size. vCores represent the logical CPU of the underlying hardware.
 
@@ -90,7 +89,7 @@ To get more details about the compute series available, refer to Azure VM docume
 
 ## Storage
 
-The storage you provision is the amount of storage capacity available to your flexible server. Storage is used for the database files, temporary files, transaction logs, and the MySQL server logs. In all compute tiers, the minimum storage supported is 20 GiB and maximum is 16 TiB. Storage is scaled in 1 GiB increments and can be scaled up after the server is created.
+The storage you provision is the amount of storage capacity available to your flexible server. Storage is used for the database files, temporary files, transaction logs, and the MySQL server logs. In all service tiers, the minimum storage supported is 20 GiB and maximum is 16 TiB. Storage is scaled in 1 GiB increments and can be scaled up after the server is created.
 
 >[!NOTE]
 > Storage can only be scaled up, not down.
@@ -113,7 +112,7 @@ We recommend that you <!--turn on storage auto-grow or to--> set up an alert to
 
 ### Storage auto-grow
 
-Storage auto-grow prevents your server from running out of storage and becoming read-only. If storage auto-grow is enabled, the storage automatically grows without impacting the workload. Storage auto-grow is enabled by default for all new server creates. For servers with less than equal to 100 GB provisioned storage, the provisioned storage size is increased by 5 GB when the free storage is below 10% of the provisioned storage. For servers with more than 100 GB of provisioned storage, the provisioned storage size is increased by 5% when the free storage space is below 10 GB of the provisioned storage size. Maximum storage limits as specified above apply. Refresh the server instance to see the updated storage provisioned in the Compute + Storage blade. 
+Storage auto-grow prevents your server from running out of storage and becoming read-only. If storage auto-grow is enabled, the storage automatically grows without impacting the workload. Storage auto-grow is enabled by default for all new server creates. For servers with less than equal to 100 GB provisioned storage, the provisioned storage size is increased by 5 GB when the free storage is below 10% of the provisioned storage. For servers with more than 100 GB of provisioned storage, the provisioned storage size is increased by 5% when the free storage space is below 10 GB of the provisioned storage size. Maximum storage limits as specified above apply. Refresh the server instance to see the updated storage provisioned under **Settings** on the **Compute + Storage** page. 
 
 For example, if you have provisioned 1000 GB of storage, and the actual utilization goes over 990 GB, the server storage size is increased to 1050 GB. Alternatively, if you have provisioned 10 GB of storage, the storage size is increase to 15 GB when less than 1 GB of storage is free.
 

articles/mysql/single-server/app-development-best-practices.md

@@ -1,12 +1,12 @@
 ---
 title: App development best practices - Azure Database for MySQL
 description: Learn about best practices for building an app by using Azure Database for MySQL.
-author: mksuni
-ms.author: sumuth
 ms.service: mysql
 ms.subservice: single-server
 ms.topic: conceptual
-ms.date: 08/11/2020
+author: mksuni
+ms.author: sumuth
+ms.date: 06/20/2022
 ---
 
 # Best practices for building an application with Azure Database for MySQL

articles/mysql/single-server/concept-monitoring-best-practices.md

@@ -1,13 +1,13 @@
 ---
 title: Monitoring best practices - Azure Database for MySQL
 description: This article describes the best practices to monitor your Azure Database for MySQL.
-author: mksuni 
-ms.author: sumuth
 ms.service: mysql
 ms.subservice: single-server
 ms.topic: conceptual
+author: mksuni 
+ms.author: sumuth
 ms.custom:
-ms.date: 11/23/2020
+ms.date: 06/20/2022
 ---
 
 # Best practices for monitoring Azure Database for MySQL - Single server

articles/mysql/single-server/concept-operation-excellence-best-practices.md

@@ -1,12 +1,12 @@
 ---
 title: MySQL server operational best practices - Azure Database for MySQL
 description: This article describes the best practices to operate your MySQL database on Azure.
-author: mksuni
-ms.author: sumuth
 ms.service: mysql
 ms.subservice: single-server
 ms.topic: conceptual
-ms.date: 11/23/2020
+author: mksuni 
+ms.author: sumuth
+ms.date: 06/20/2022
 ---
 
 # Best practices for server operations on Azure Database for MySQL -Single server

articles/mysql/single-server/concept-performance-best-practices.md

@@ -1,12 +1,12 @@
 ---
 title: Performance best practices - Azure Database for MySQL
 description: This article describes some recommendations to monitor and tune performance for your Azure Database for MySQL.
-author: Bashar-MSFT
-ms.author: bahusse
 ms.service: mysql
 ms.subservice: single-server
 ms.topic: conceptual
-ms.date: 1/28/2021
+author: Bashar-MSFT
+ms.author: bahusse
+ms.date: 06/20/2022
 ---
 
 # Best practices for optimal performance of your Azure Database for MySQL - Single server

articles/mysql/single-server/concept-reserved-pricing.md

@@ -1,12 +1,12 @@
 ---
 title: Prepay for compute with reserved capacity - Azure Database for MySQL 
 description: Prepay for Azure Database for MySQL compute resources with reserved capacity
-author: mksuni
-ms.author: sumuth
 ms.service: mysql
 ms.subservice: single-server
 ms.topic: conceptual
-ms.date: 10/06/2021
+author: mksuni
+ms.author: sumuth
+ms.date: 06/20/2022
 ---
 
 # Prepay for Azure Database for MySQL compute resources with reserved instances
@@ -18,7 +18,6 @@ Azure Database for MySQL now helps you save money by prepaying for compute resou
 >[!NOTE]
 >The Reserved instances (RI) feature in Azure Database for MySQL – Flexible server is not working properly for the Business Critical service tier, after its rebranding > from the Memory Optimized service tier. Specifically, instance reservation has stopped working, and we are currently working to fix the issue.
 
-
 ## How does the instance reservation work?
 You do not need to assign the reservation to specific Azure Database for MySQL servers. An already running Azure Database for MySQL or ones that are newly deployed, will automatically get the benefit of reserved pricing. By purchasing a reservation, you are pre-paying for the compute costs for a period of one or three years. As soon as you buy a reservation, the Azure database for MySQL compute charges that match the reservation attributes are no longer charged at the pay-as-you go rates. A reservation does not cover software, networking, or storage charges associated with the MySQL Database server. At the end of the reservation term, the billing benefit expires, and the Azure Database for MySQL are billed at the pay-as-you go price. Reservations do not auto-renew. For pricing information, see the [Azure Database for MySQL reserved capacity offering](https://azure.microsoft.com/pricing/details/mysql/). </br>
 

articles/mysql/single-server/concepts-aks.md

@@ -1,15 +1,14 @@
 ---
 title: Connect to Azure Kubernetes Service - Azure Database for MySQL
 description: Learn about connecting Azure Kubernetes Service with Azure Database for MySQL
-author: savjani
-ms.author: pariks
 ms.service: mysql
 ms.subservice: single-server
 ms.topic: conceptual
-ms.date: 07/14/2020
+author: savjani
+ms.author: pariks
+ms.date: 06/20/2022
 ---
 
-
 # Best practices for Azure Kubernetes Service and Azure Database for MySQL
 
 [!INCLUDE[applies-to-mysql-single-server](../includes/applies-to-mysql-single-server.md)]