Merge pull request #98400 from ajlam/master

K50 doc updates for mysql and mariadb

Author: megvanhuygen

articles/mariadb/concepts-audit-logs.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 12/09/2019
 ---
 
 # Audit Logs in Azure Database for MariaDB
@@ -22,6 +22,9 @@ By default the audit log is disabled. To enable it, set `audit_log_enabled` to O
 Other parameters you can adjust include:
 
 - `audit_log_events`: controls the events to be logged. See below table for specific audit events.
+- `audit_log_include_users`: MariaDB users to be included for logging. The default value for this parameter is empty, which will include all the users for logging. This has higher priority over `audit_log_exclude_users`. Max length of the parameter is 512 characters.
+> [!Note]
+> `audit_log_include_users` has higher priority over `audit_log_exclude_users`. For example, if `audit_log_include_users` = `demouser` and `audit_log_exclude_users` = `demouser`, the user will be included in the audit logs because `audit_log_include_users` has higher priority.
 - `audit_log_exclude_users`: MariaDB users to be excluded from logging. Allows for at most four users. Max length of the parameter is 256 characters.
 
 | **Event** | **Description** |

articles/mariadb/concepts-limits.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 12/09/2019
 ---
 # Limitations in Azure Database for MariaDB
 The following sections describe capacity, storage engine support, privilege support, data manipulation statement support, and functional limits in the database service.
@@ -17,17 +17,17 @@ The maximum number of connections per pricing tier and vCores are as follows:
 |---|---|---|
 |Basic| 1| 50|
 |Basic| 2| 100|
-|General Purpose| 2| 300|
-|General Purpose| 4| 625|
-|General Purpose| 8| 1250|
-|General Purpose| 16| 2500|
-|General Purpose| 32| 5000|
-|General Purpose| 64| 10000|
-|Memory Optimized| 2| 600|
-|Memory Optimized| 4| 1250|
-|Memory Optimized| 8| 2500|
-|Memory Optimized| 16| 5000|
-|Memory Optimized| 32| 10000|
+|General Purpose| 2| 600|
+|General Purpose| 4| 1250|
+|General Purpose| 8| 2500|
+|General Purpose| 16| 5000|
+|General Purpose| 32| 10000|
+|General Purpose| 64| 20000|
+|Memory Optimized| 2| 800|
+|Memory Optimized| 4| 2500|
+|Memory Optimized| 8| 5000|
+|Memory Optimized| 16| 10000|
+|Memory Optimized| 32| 20000|
 
 When connections exceed the limit, you may receive the following error:
 > ERROR 1040 (08004): Too many connections

articles/mariadb/howto-server-parameters.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/05/2019
+ms.date: 12/9/2019
 ---
 
 # How to configure server parameters in Azure Database for MariaDB by using the Azure portal
@@ -32,21 +32,21 @@ The list of supported server parameters is constantly growing. Use the server pa
 
 InnoDB Buffer Pool and Max Connections are not configurable and tied to your [pricing tier](concepts-pricing-tiers.md).
 
-|**Pricing Tier**| **vCore(s)**|**InnoDB Buffer Pool (MB)**| **Max Connections**|
-|---|---|---|---|
-|Basic| 1| 1024| 50|
-|Basic| 2| 2560| 100|
-|General Purpose| 2| 3584| 300|
-|General Purpose| 4| 7680| 625|
-|General Purpose| 8| 15360| 1250|
-|General Purpose| 16| 31232| 2500|
-|General Purpose| 32| 62976| 5000|
-|General Purpose| 64| 125952| 10000|
-|Memory Optimized| 2| 7168| 600|
-|Memory Optimized| 4| 15360| 1250|
-|Memory Optimized| 8| 30720| 2500|
-|Memory Optimized| 16| 62464| 5000|
-|Memory Optimized| 32| 125952| 10000|
+|**Pricing Tier**| **vCore(s)**|**InnoDB Buffer Pool (MB)**|
+|---|---|---|
+|Basic| 1| 1024|
+|Basic| 2| 2560|
+|General Purpose| 2| 3584|
+|General Purpose| 4| 7680|
+|General Purpose| 8| 15360|
+|General Purpose| 16| 31232|
+|General Purpose| 32| 62976|
+|General Purpose| 64| 125952|
+|Memory Optimized| 2| 7168|
+|Memory Optimized| 4| 15360|
+|Memory Optimized| 8| 30720|
+|Memory Optimized| 16| 62464|
+|Memory Optimized| 32| 125952|
 
 These additional server parameters are not configurable in the system:
 

articles/mysql/concepts-audit-logs.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mysql
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 12/09/2019
 ---
 
 # Audit Logs in Azure Database for MySQL
@@ -24,7 +24,7 @@ Other parameters you can adjust include:
 - `audit_log_events`: controls the events to be logged. See below table for specific audit events.
 - `audit_log_include_users`: MySQL users to be included for logging. The default value for this parameter is empty, which will include all the users for logging. This has higher priority over `audit_log_exclude_users`. Max length of the parameter is 512 characters.
 > [!Note]
-> `audit_log_include_users` has higher priority over `audit_log_exclude_users` for example If audit_log_include_users = `demouser` and audit_log_exclude_users = `demouser`, it will audit the logs because `audit_log_include_users` has higher priority.
+> `audit_log_include_users` has higher priority over `audit_log_exclude_users`. For example, if `audit_log_include_users` = `demouser` and `audit_log_exclude_users` = `demouser`, the user will be included in the audit logs because `audit_log_include_users` has higher priority.
 - `audit_log_exclude_users`: MySQL users to be excluded from logging. Max length of the parameter is 512 characters.
 
 > [!Note]

articles/mysql/concepts-limits.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mysql
 ms.topic: conceptual
-ms.date: 12/2/2019
+ms.date: 12/9/2019
 ---
 # Limitations in Azure Database for MySQL
 The following sections describe capacity, storage engine support, privilege support, data manipulation statement support, and functional limits in the database service. Also see [general limitations](https://dev.mysql.com/doc/mysql-reslimits-excerpt/5.6/en/limits.html) applicable to the MySQL database engine.
@@ -17,17 +17,17 @@ The maximum number of connections per pricing tier and vCores are as follows:
 |---|---|---|
 |Basic| 1| 50|
 |Basic| 2| 100|
-|General Purpose| 2| 300|
-|General Purpose| 4| 625|
-|General Purpose| 8| 1250|
-|General Purpose| 16| 2500|
-|General Purpose| 32| 5000|
-|General Purpose| 64| 10000|
-|Memory Optimized| 2| 600|
-|Memory Optimized| 4| 1250|
-|Memory Optimized| 8| 2500|
-|Memory Optimized| 16| 5000|
-|Memory Optimized| 32| 10000|
+|General Purpose| 2| 600|
+|General Purpose| 4| 1250|
+|General Purpose| 8| 2500|
+|General Purpose| 16| 5000|
+|General Purpose| 32| 10000|
+|General Purpose| 64| 20000|
+|Memory Optimized| 2| 1250|
+|Memory Optimized| 4| 2500|
+|Memory Optimized| 8| 5000|
+|Memory Optimized| 16| 10000|
+|Memory Optimized| 32| 20000|
 
 When connections exceed the limit, you may receive the following error:
 > ERROR 1040 (08004): Too many connections

articles/mysql/concepts-server-logs.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mysql
 ms.topic: conceptual
-ms.date: 05/29/2019
+ms.date: 12/09/2019
 ---
 # Slow query logs in Azure Database for MySQL
 In Azure Database for MySQL, the slow query log is available to users. Access to the transaction log is not supported. The slow query log can be used to identify performance bottlenecks for troubleshooting.
@@ -19,6 +19,8 @@ In the Azure portal, select your Azure Database for MySQL server. Under the **Mo
 
 For more information on Azure CLI, see [Configure and access slow query logs using Azure CLI](howto-configure-server-logs-in-cli.md).
 
+Similarly, you can pipe the logs to Azure Monitor using Diagnostic Logs. See [below](concepts-server-logs.md#diagnostic-logs) for more information.
+
 ## Log retention
 Logs are available for up to seven days from their creation. If the total size of the available logs exceeds 7 GB, then the oldest files are deleted until space is available. 
 
@@ -33,6 +35,7 @@ Other parameters you can adjust include:
 - **log_slow_admin_statements**: if ON includes administrative statements like ALTER_TABLE and ANALYZE_TABLE in the statements written to the slow_query_log.
 - **log_queries_not_using_indexes**: determines whether queries that do not use indexes are logged to the slow_query_log
 - **log_throttle_queries_not_using_indexes**: This parameter limits the number of non-index queries that can be written to the slow query log. This parameter takes effect when log_queries_not_using_indexes is set to ON.
+- **log_output**: if "File", allows the slow query log to be written to both the local server storage and to Azure Monitor Diagnostic Logs. If "None", the slow query log will only be written to the local server storage. 
 
 > [!Note]
 > For `sql_text`, log will be truncated if it exceeds 2048 characters.

articles/mysql/concepts-supported-versions.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mysql
 ms.topic: conceptual
-ms.date: 09/12/2019
+ms.date: 12/09/2019
 ---
 # Supported Azure Database for MySQL server versions
 
@@ -20,15 +20,15 @@ Azure Database for MySQL currently supports the following versions:
 
 ## MySQL Version 5.6
 
-Bug fix release: 5.6.44
+Bug fix release: 5.6.45
 
-Refer to the MySQL [release notes](https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-44.html) to learn more about improvements and fixes in this version.
+Refer to the MySQL [release notes](https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-45.html) to learn more about improvements and fixes in this version.
 
 ## MySQL Version 5.7
 
-Bug fix release: 5.7.26
+Bug fix release: 5.7.27
 
-Refer to the MySQL [release notes](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-26.html) to learn more about improvements and fixes in this version.
+Refer to the MySQL [release notes](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-27.html) to learn more about improvements and fixes in this version.
 
 ## MySQL Version 8.0