Merge pull request #80881 from ajlam/master

GitHubber17 · web-flow · commit c05c65e38980 · 2019-06-27T19:42:53.000-07:00
Update iPerf MySQL &amp; MariaDB
diff --git a/articles/mariadb/concepts-performance-recommendations.md b/articles/mariadb/concepts-performance-recommendations.md
@@ -5,14 +5,14 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 06/12/2019
+ms.date: 06/27/2019
 ---
 # Performance Recommendations in Azure Database for MariaDB
 
-**Applies to:** Azure Database for MariaDB 10.2s
+**Applies to:** Azure Database for MariaDB 10.2
 
 > [!NOTE]
-> Performance Recommendations is in preview. Support for Performance Recommendations in the Azure portal is being rolled out and may not yet be available in your region.
+> Performance Recommendations is in preview.
 
 The Performance Recommendations feature analyzes your databases to create customized suggestions for improved performance. To produce the recommendations, the analysis looks at various database characteristics including schema. Enable [Query Store](concepts-query-store.md) on your server to fully utilize the Performance Recommendations feature. If performance schema is OFF, turning on Query Store enables performance_schema and a subset of performance schema instruments required for the feature. After implementing any performance recommendation, you should test performance to evaluate the impact of those changes.
 
diff --git a/articles/mariadb/concepts-query-performance-insight.md b/articles/mariadb/concepts-query-performance-insight.md
@@ -5,17 +5,29 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 06/12/2019
+ms.date: 06/27/2019
 ---
 # Query Performance Insight in Azure Database for MariaDB
 
 **Applies to:** Azure Database for MariaDB 10.2
 
 > [!NOTE]
-> Query Performance Insight is in preview. Support for Query Performance Insight in the Azure portal is being rolled out and may not yet be available in your region.
+> Query Performance Insight is in preview.
 
 Query Performance Insight helps you to quickly identify what your longest running queries are, how they change over time, and what waits are affecting them.
 
+## Common scenarios
+
+### Long running queries
+
+- Identifying longest running queries in the past X hours
+- Identifying top N queries that are waiting on resources
+ 
+### Wait statistics
+
+- Understanding wait nature for a query
+- Understanding trends for resource waits and where resource contention exists
+
 ## Permissions
 
 **Owner** or **Contributor** permissions required to view the text of the queries in Query Performance Insight. **Reader** can view charts and tables but not query text.
@@ -30,12 +42,21 @@ The [Query Performance Insight](concepts-query-performance-insight.md) view in t
 
 In the portal page of your Azure Database for MariaDB server, select **Query Performance Insight** under the **Intelligent Performance** section of the menu bar.
 
-![Query Performance Insight long running queries](./media/concepts-query-performance-insight/query-performance-insight-landing-page.png)
+### Long running queries
 
 The **Long running queries** tab shows the top 5 queries by average duration per execution, aggregated in 15-minute intervals. You can view more queries by selecting from  the **Number of Queries** drop down. The chart colors may change for a specific Query ID when you do this.
 
 You can click and drag in the chart to narrow down to a specific time window. Alternatively, use the zoom in and out icons to view a smaller or larger time period respectively.
 
+![Query Performance Insight long running queries](./media/concepts-query-performance-insight/query-performance-insight-landing-page.png)
+
+### Wait statistics 
+
+> [!NOTE]
+> Wait statistics are meant for troubleshooting query performance issues. It is recommended to be turned on only for troubleshooting purposes.
+
+Wait statistics provides a view of the wait events that occur during the execution of a specific query. Learn more about the wait event types in the [MySQL engine documentation](https://go.microsoft.com/fwlink/?linkid=2098206).
+
 Select the **Wait Statistics** tab to view the corresponding visualizations on waits in the server.
 
 Queries displayed in the wait statistics view are grouped by the queries that exhibit the largest waits during the specified time interval.
diff --git a/articles/mariadb/concepts-query-store.md b/articles/mariadb/concepts-query-store.md
@@ -5,14 +5,14 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 06/12/2019
+ms.date: 06/27/2019
 ---
 # Monitor Azure Database for MariaDB performance with Query Store
 
 **Applies to:** Azure Database for MariaDB 10.2
 
 > [!NOTE]
-> Query Store is in preview. Support for Query Store in the Azure portal is being rolled out and may not yet be available in your region.
+> Query Store is in preview.
 
 The Query Store feature in Azure Database for Mariadb provides a way to track query performance over time. Query Store simplifies performance troubleshooting by helping you quickly find the longest running and most resource-intensive queries. Query Store automatically captures a history of queries and runtime statistics, and it retains them for your review. It separates data by time windows so that you can see database usage patterns. Data for all users, databases, and queries is stored in the **mysql** schema database in the Azure Database for MariaDB instance.
 
@@ -23,10 +23,6 @@ Query store can be used in a number of scenarios, including the following:
 - Detecting regressed queries
 - Determining the number of times a query was executed in a given time window
 - Comparing the average execution time of a query across time windows to see large deltas
-- Identifying longest running queries in the past X hours
-- Identifying top N queries that are waiting on resources
-- Understanding wait nature for a query
-- Understanding trends for resource waits and where resource contention exists
 
 ## Enabling Query Store
 
diff --git a/articles/mysql/concepts-performance-recommendations.md b/articles/mysql/concepts-performance-recommendations.md
@@ -5,14 +5,14 @@ author: ajlam
 ms.author: andrela
 ms.service: mysql
 ms.topic: conceptual
-ms.date: 05/23/2019
+ms.date: 06/27/2019
 ---
 # Performance Recommendations in Azure Database for MySQL
 
 **Applies to:** Azure Database for MySQL 5.7
 
 > [!NOTE]
-> Performance Recommendations is in preview. Support for Performance Recommendations in the Azure portal is being rolled out and may not yet be available in your region.
+> Performance Recommendations is in preview.
 
 The Performance Recommendations feature analyzes your databases to create customized suggestions for improved performance. To produce the recommendations, the analysis looks at various database characteristics including schema. Enable [Query Store](concepts-query-store.md) on your server to fully utilize the Performance Recommendations feature. If performance schema is OFF, turning on Query Store enables performance_schema and a subset of performance schema instruments required for the feature. After implementing any performance recommendation, you should test performance to evaluate the impact of those changes.
 
diff --git a/articles/mysql/concepts-query-performance-insight.md b/articles/mysql/concepts-query-performance-insight.md
@@ -5,17 +5,29 @@ author: ajlam
 ms.author: andrela
 ms.service: MySQL
 ms.topic: conceptual
-ms.date: 06/05/2019
+ms.date: 06/27/2019
 ---
 # Query Performance Insight in Azure Database for MySQL
 
 **Applies to:** Azure Database for MySQL 5.7
 
 > [!NOTE]
-> Query Performance Insight is in preview. Support for Query Performance Insight in the Azure portal is being rolled out and may not yet be available in your region.
+> Query Performance Insight is in preview.
 
 Query Performance Insight helps you to quickly identify what your longest running queries are, how they change over time, and what waits are affecting them.
 
+## Common scenarios
+
+### Long running queries
+
+- Identifying longest running queries in the past X hours
+- Identifying top N queries that are waiting on resources
+ 
+### Wait statistics
+
+- Understanding wait nature for a query
+- Understanding trends for resource waits and where resource contention exists
+
 ## Permissions
 
 **Owner** or **Contributor** permissions required to view the text of the queries in Query Performance Insight. **Reader** can view charts and tables but not query text.
@@ -30,12 +42,21 @@ The [Query Performance Insight](concepts-query-performance-insight.md) view in t
 
 In the portal page of your Azure Database for MySQL server, select **Query Performance Insight** under the **Intelligent Performance** section of the menu bar.
 
-![Query Performance Insight long running queries](./media/concepts-query-performance-insight/query-performance-insight-landing-page.png) 
+### Long running queries
 
 The **Long running queries** tab shows the top 5 queries by average duration per execution, aggregated in 15-minute intervals. You can view more queries by selecting from  the **Number of Queries** drop down. The chart colors may change for a specific Query ID when you do this.
 
 You can click and drag in the chart to narrow down to a specific time window. Alternatively, use the zoom in and out icons to view a smaller or larger time period respectively.
 
+![Query Performance Insight long running queries](./media/concepts-query-performance-insight/query-performance-insight-landing-page.png) 
+
+### Wait statistics
+
+> [!NOTE]
+> Wait statistics are meant for troubleshooting query performance issues. It is recommended to be turned on only for troubleshooting purposes.
+
+Wait statistics provides a view of the wait events that occur during the execution of a specific query. Learn more about the wait event types in the [MySQL engine documentation](https://go.microsoft.com/fwlink/?linkid=2098206).
+
 Select the **Wait Statistics** tab to view the corresponding visualizations on waits in the server.
 
 Queries displayed in the wait statistics view are grouped by the queries that exhibit the largest waits during the specified time interval.
diff --git a/articles/mysql/concepts-query-store.md b/articles/mysql/concepts-query-store.md
@@ -5,14 +5,14 @@ author: ajlam
 ms.author: andrela
 ms.service: mysql
 ms.topic: conceptual
-ms.date: 06/05/2019
+ms.date: 06/27/2019
 ---
 # Monitor Azure Database for MySQL performance with Query Store
 
 **Applies to:** Azure Database for MySQL 5.7
 
 > [!NOTE]
-> Query Store is in preview. Support for Query Store in the Azure portal is being rolled out and may not yet be available in your region.
+> Query Store is in preview.
 
 The Query Store feature in Azure Database for MySQL provides a way to track query performance over time. Query Store simplifies performance troubleshooting by helping you quickly find the longest running and most resource-intensive queries. Query Store automatically captures a history of queries and runtime statistics, and it retains them for your review. It separates data by time windows so that you can see database usage patterns. Data for all users, databases, and queries is stored in the **mysql** schema database in the Azure Database for MySQL instance.
 
@@ -23,10 +23,6 @@ Query store can be used in a number of scenarios, including the following:
 - Detecting regressed queries
 - Determining the number of times a query was executed in a given time window
 - Comparing the average execution time of a query across time windows to see large deltas
-- Identifying longest running queries in the past X hours
-- Identifying top N queries that are waiting on resources
-- Understanding wait nature for a query
-- Understanding trends for resource waits and where resource contention exists
 
 ## Enabling Query Store
 
