Merge pull request #178161 from MicrosoftDocs/release-mysql-flexible-server-ga

Release mysql flexible server ga--scheduled release at 10AM of 11/02

Author: huypub

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

@@ -19,7 +19,7 @@
     {
         "source_path_from_root": "/articles/mysql/flexible-server/how-to-configure-slow-query-logs-portal.md",
         "redirect_url": "/azure/mysql/flexible-server/tutorial-query-performance-insights",
-        "redirect_document_id": false
+        "redirect_document_id": false 
     }
 ]
 }

articles/mysql/TOC.yml

@@ -133,7 +133,7 @@
     - name: Networking
       items:
       - name: Virtual Network Service Endpoints
-        href: concepts-data-access-and-security-vnet.md 
+        href: concepts-data-access-and-security-vnet.md
       - name: Private link
         href: concepts-data-access-security-private-link.md
     - name: Security
@@ -172,7 +172,7 @@
       - name: High availability
         href: concepts-high-availability.md
         displayName: backup, restore,high availability
-    - name: Server Management 
+    - name: Server Management
       items:
       - name: Servers
         href: concepts-servers.md
@@ -301,7 +301,7 @@
       - name: Configuring Audit Logs using Azure CLI
         href: howto-configure-audit-logs-cli.md
         displayName: debug, audit log
-    - name: Server Management 
+    - name: Server Management
       items:
       - name: Manage and scale a server
         items:
@@ -387,8 +387,8 @@
     - name: Azure CLI samples
       href: sample-scripts-azure-cli.md
     - name: Configure Java connection pooling
-      href: sample-scripts-java-connection-pooling.md    
-- name: Flexible Server (Preview)
+      href: sample-scripts-java-connection-pooling.md
+- name: Flexible Server
   items:
   - name: Flexible Server documentation
     href: flexible-server/index.yml
@@ -411,7 +411,7 @@
             displayName: Resource Manager
             href: flexible-server/quickstart-create-arm-template.md
       - name: Connect and query
-        items:          
+        items:
           - name: Azure CLI
             href: flexible-server/connect-azure-cli.md
           - name: PHP
@@ -424,7 +424,7 @@
             href: flexible-server/connect-java.md
           - name: .NET
             href: flexible-server/connect-csharp.md
-          - name: Connect to server in VNET 
+          - name: Connect to server in VNET
             href: flexible-server/quickstart-create-connect-server-vnet.md
       - name: Connect using TLS/SSL
         href: flexible-server/how-to-connect-tls-ssl.md
@@ -445,20 +445,20 @@
     - name: Server Management
       items:
       - name: Servers
-        href: flexible-server/concept-servers.md 
+        href: flexible-server/concept-servers.md
       - name: Server parameters
         href: flexible-server/concepts-server-parameters.md
       - name: Limitations
         href: flexible-server/concepts-limitations.md
     - name: Networking
       items:
-      - name: Networking concepts 
+      - name: Networking concepts
         href: flexible-server/concepts-networking.md
         displayName: virtual network, IP address, public access
-      - name: Private Access 
+      - name: Private Access
         href: flexible-server/concepts-networking-vnet.md
         displayName: virtual network
-      - name: Public Access 
+      - name: Public Access
         href: flexible-server/concepts-networking-public.md
         displayName: Public access,
     - name: Service Maintenance
@@ -491,7 +491,7 @@
     - name: Backup & Restore
       items:
       - name: Backup & Restore concepts
-        href: flexible-server/concepts-backup-restore.md    
+        href: flexible-server/concepts-backup-restore.md
   - name: Tutorials
     items:
     - name: Application Development
@@ -517,12 +517,12 @@
         - name: Azure CLI
           href: flexible-server/how-to-manage-server-cli.md
       - name: Stop/start server
-        items: 
+        items:
         - name: Azure portal
           href: flexible-server/how-to-stop-start-server-portal.md
         - name: Azure CLI
           href: flexible-server/how-to-restart-stop-start-server-cli.md
-      - name: Restart server 
+      - name: Restart server
         items:
         - name: Azure portal
           href: flexible-server/how-to-restart-server-portal.md
@@ -575,10 +575,10 @@
           href: flexible-server/how-to-read-replicas-cli.md
     - name: Backup & Restore
       items:
-      - name: Restore a server 
-        items: 
+      - name: Restore a server
+        items:
         - name: Azure portal
-          href: flexible-server/how-to-restore-server-portal.md  
+          href: flexible-server/how-to-restore-server-portal.md
         - name: Azure CLI
           href: flexible-server/how-to-restore-server-cli.md
     - name: Troubleshooting

articles/mysql/flexible-server/concept-servers.md

@@ -8,13 +8,10 @@ ms.topic: conceptual
 ms.date: 09/21/2020
 ---
 
-# Server concepts in Azure Database for MySQL Flexible Server (Preview)
+# Server concepts in Azure Database for MySQL Flexible Server
 
 [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
-> [!IMPORTANT] 
-> Azure Database for MySQL - Flexible Server is currently in public preview.
-
 This article provides considerations and guidelines for working with Azure Database for MySQL Flexible Servers.
 
 ## What is an Azure Database for MySQL Flexible Server?

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

@@ -12,17 +12,14 @@ ms.date: 9/21/2020
 
 [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
-> [!IMPORTANT]
-> Azure Database for MySQL Flexible Server is currently in public preview
-
 Azure Database for MySQL Flexible Server provides users with the ability to configure audit logs. Audit logs can be used to track database-level activity including connection, admin, DDL, and DML events. These types of logs are commonly used for compliance purposes.
 
 ## Configure audit logging
 
 >[!IMPORTANT]
 > It is recommended to only log the event types and users required for your auditing purposes to ensure your server's performance is not heavily impacted.
 
-By default, audit logs are disabled. To enable them, set the `audit_log_enabled` server parameter to *ON*. This can be configured using the Azure portal or Azure CLI <!-- add link to server parameter-->. 
+By default, audit logs are disabled. To enable them, set the `audit_log_enabled` server parameter to *ON*. This can be configured using the Azure portal or Azure CLI <!-- add link to server parameter-->.
 
 Other parameters you can adjust to control audit logging behavior include:
 
@@ -148,8 +145,8 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
     AzureDiagnostics
     | where LogicalServerName_s == '<your server name>'
     | where Category == 'MySqlAuditLogs' and event_class_s == "general_log"
-    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s 
-    | order by TimeGenerated asc nulls last 
+    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s
+    | order by TimeGenerated asc nulls last
     ```
 
 - List CONNECTION events on a particular server
@@ -158,7 +155,7 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
     AzureDiagnostics
     | where LogicalServerName_s == '<your server name>'
     | where Category == 'MySqlAuditLogs' and event_class_s == "connection_log"
-    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s 
+    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s
     | order by TimeGenerated asc nulls last
     ```
 
@@ -168,7 +165,7 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
     AzureDiagnostics
     | where LogicalServerName_s == '<your server name>'
     | where Category == 'MySqlAuditLogs'
-    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s 
+    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s
     | summarize count() by event_class_s, event_subclass_s, user_s, ip_s
     ```
 
@@ -178,19 +175,19 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
     AzureDiagnostics
     | where LogicalServerName_s == '<your server name>'
     | where Category == 'MySqlAuditLogs'
-    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s 
+    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s
     | summarize count() by LogicalServerName_s, bin(TimeGenerated, 5m)
-    | render timechart 
+    | render timechart
     ```
 
 - List audited events across all MySQL servers with Diagnostic Logs enabled for audit logs
 
     ```kusto
     AzureDiagnostics
     | where Category == 'MySqlAuditLogs'
-    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s 
+    | project TimeGenerated, LogicalServerName_s, event_class_s, event_subclass_s, event_time_t, user_s , ip_s , sql_text_s
     | order by TimeGenerated asc nulls last
-    ``` 
+    ```
 
 ## Next steps
 - Learn more about [slow query logs](concepts-slow-query-logs.md)

articles/mysql/flexible-server/concepts-backup-restore.md

@@ -8,13 +8,10 @@ ms.topic: conceptual
 ms.date: 09/21/2020
 ---
 
-# Backup and restore in Azure Database for MySQL Flexible Server (Preview)
+# Backup and restore in Azure Database for MySQL Flexible Server
 
 [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
-> [!IMPORTANT]
-> Azure Database for MySQL - Flexible Server is currently in public preview.
-
 Azure Database for MySQL Flexible Server, automatically creates server backups and securely stores them in local redundant storage within the region. Backups can be used to restore your server to a point-in-time. Backup and restore are an essential part of any business continuity strategy because they protect your data from accidental corruption or deletion.
 
 ## Backup overview
@@ -146,7 +143,7 @@ After a restore from either **latest restore point** or **custom restore point**
 ### Backup related questions
 
 - **How do I backup my server?**
-By default, Azure Database for MySQL enables automated backups of your entire server (encompassing all databases created) with a default 7 day retention period. The only way to manually take a backup is by using community tools such as mysqldump as documented [here](../concepts-migrate-dump-restore.md#dump-and-restore-using-mysqldump-utility) or mydumper as documented [here](../concepts-migrate-mydumper-myloader.md#create-a-backup-using-mydumper). If you wish to backup Azure Database for MySQL to a Blob storage, refer to our tech community blog [Backup Azure Database for MySQL to a Blob Storage](https://techcommunity.microsoft.com/t5/azure-database-for-mysql/backup-azure-database-for-mysql-to-a-blob-storage/ba-p/803830). 
+By default, Azure Database for MySQL enables automated backups of your entire server (encompassing all databases created) with a default 7 day retention period. The only way to manually take a backup is by using community tools such as mysqldump as documented [here](../concepts-migrate-dump-restore.md#dump-and-restore-using-mysqldump-utility) or mydumper as documented [here](../concepts-migrate-mydumper-myloader.md#create-a-backup-using-mydumper). If you wish to backup Azure Database for MySQL to a Blob storage, refer to our tech community blog [Backup Azure Database for MySQL to a Blob Storage](https://techcommunity.microsoft.com/t5/azure-database-for-mysql/backup-azure-database-for-mysql-to-a-blob-storage/ba-p/803830).
 
 - **Can I configure automatic backups to be retained for long term?**
 No, currently we only support a maximum of 35 days of automated backup retention. You can take manual backups and use that for long-term retention requirement.
@@ -155,7 +152,7 @@ No, currently we only support a maximum of 35 days of automated backup retention
 The first snapshot backup is scheduled immediately after a server is created. Snapshot backups are taken daily once. Transaction log backups occur every five minutes. Backup windows are inherently managed by Azure and cannot be customized.
 
 - **Are my backups encrypted?**
-All Azure Database for MySQL data, backups and temporary files created during query execution are encrypted using AES 256-bit encryption. The storage encryption is always on and cannot be disabled. 
+All Azure Database for MySQL data, backups and temporary files created during query execution are encrypted using AES 256-bit encryption. The storage encryption is always on and cannot be disabled.
 
 - **Can I restore a single/few database(s)?**
 Restoring a single/few database(s) or tables is not supported. In case you want to restore specific databases, perform a Point in Time Restore and then extract the table(s) or database(s) needed.
@@ -185,20 +182,20 @@ Flexible server provides up to 100% of your provisioned server storage as backup
 No new backups are performed for stopped servers. All older backups (within the retention window) at the time of stopping the server are retained until the server is restarted post which backup retention for the active server is governed by it’s backup retention window.
 
 - **How will I be billed for backups for a stopped server?**
-While your server instance is stopped, you are charged for provisioned storage (including Provisioned IOPS) and backup storage (backups stored within your specified retention window). Free backup storage is limited to the size of your provisioned database and only applies to active servers. 
+While your server instance is stopped, you are charged for provisioned storage (including Provisioned IOPS) and backup storage (backups stored within your specified retention window). Free backup storage is limited to the size of your provisioned database and only applies to active servers.
 
 ### Restore related questions
 
 - **How do I restore my server?**
 Azure portal supports Point In Time Restore (for all servers) allowing users to restore to latest or custom restore point. To manually restore your server from the backups taken by mysqldump/myDumper read [Restore your database using myLoader](../concepts-migrate-mydumper-myloader.md#restore-your-database-using-myloader).
 
 - **Why is my restore taking so much time?**
-The estimated time for the recovery of the server depends on several factors: 
+The estimated time for the recovery of the server depends on several factors:
    - The size of the databases. As a part of the recovery process, the database needs to be hydrated from the last physical backup and hence the time taken to recover will be proportional to the size of the database.
    - The active portion of transaction activity that needs to be replayed to recover. Recovery can take longer depending on the additional transaction activity from the last successful checkpoint.
-   - The network bandwidth if the restore is to a different region 
-   - The number of concurrent restore requests being processed in the target region 
-   - The presence of primary key in the tables in the database. For faster recovery, consider adding primary key for all the tables in your database.  
+   - The network bandwidth if the restore is to a different region
+   - The number of concurrent restore requests being processed in the target region
+   - The presence of primary key in the tables in the database. For faster recovery, consider adding primary key for all the tables in your database.
 
 
 ## Next steps

articles/mysql/flexible-server/concepts-business-continuity.md

@@ -8,13 +8,10 @@ ms.topic: conceptual
 ms.date: 09/21/2020
 ---
 
-# Overview of business continuity with Azure Database for MySQL - Flexible Server (Preview)
+# Overview of business continuity with Azure Database for MySQL - Flexible Server
 
 [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
-> [!IMPORTANT]
-> Azure Database for MySQL - Flexible Server is currently in public preview.
-
 Azure Database for MySQL Flexible Server enables business continuity capabilities that protect your databases in the event of a planned and unplanned outage. Features such as automated backups and high availability addresses different levels of fault-protection with different recovery time and data loss exposures. As you architect your application to protect against faults, you should consider the recovery time objective (RTO) and recovery point objective (RPO) for each application. RTO is the downtime tolerance and RPO is the data loss tolerance after a disruption to the database service.
 
 The table below illustrates the features that Flexible server offers.
@@ -27,9 +24,6 @@ The table below illustrates the features that Flexible server offers.
 | **Zone redundant high availability** | Flexible server can be deployed in high availability mode, which deploys primary and standby servers in two different availability zones within a region. This protects from zone-level failures and also helps with reducing application downtime during planned and unplanned downtime events. Data from the primary server is synchronously replicated to the standby replica. During any downtime event, the database server is automatically failed over to the standby replica. Refer to [Concepts - High availability](./concepts-high-availability.md) for more details. | Supported in general purpose and memory optimized compute tiers. Available only in regions where multiple zones are available.|
 | **Premium file shares** | Database files are stored in a highly durable and reliable Azure premium file shares that provide data redundancy with three copies of replica stored within an availability zone with automatic data recovery capabilities. Refer to [Premium File shares](../../storage/files/storage-how-to-create-file-share.md) for more details. | Data stored within an availability zone |
 
-> [!IMPORTANT]
-> No uptime, RTO and RPO SLA are offered during preview period. Details provided in this page for your information and planning purposes only.
-
 ## Planned downtime mitigation
 
 Here are some planned maintenance scenarios that incur downtime:
@@ -58,7 +52,6 @@ Here are some unplanned failure scenarios and the recovery process:
 | **Availability zone failure** | While it is a rare event, if you want to recover from a zone-level failure, you can perform point-in-time recovery using the backup and choosing custom restore point to get to the latest data. A new flexible server will be deployed in another zone. The time taken to restore depends on the previous backup and the number of transaction logs to recover. | Flexible server performs automatic failover to the standby site. Refer to [HA concepts page](./concepts-high-availability.md) for more details. |
 | **Region failure** | While it is a rare event, if you want to recover from a region-level failure, you can perform database recovery by creating a new server using the latest geo-redundant backup available under the same subscription to get to the latest data. A new flexible server will be deployed to the selected region. The time taken to restore depends on the previous backup and the number of transaction logs to recover. | While it is a rare event, if you want to recover from a region-level failure, you can perform database recovery by creating a new server using the latest geo-redundant backup available under the same subscription to get to the latest data. The target flexible server for an existing HA server will be deployed as a Non-HA server to the Azure paired region. The time taken to restore depends on the previous backup and the number of transaction logs to recover. |
 
-
 > [!IMPORTANT]
 > Deleted servers **cannot** be restored. If you delete the server, all databases that belong to the server are also deleted and cannot be recovered. Use [Azure resource lock](../../azure-resource-manager/management/lock-resources.md) to help prevent accidental deletion of your server.