|
| 1 | +--- |
| 2 | +title: Performance recommendations in Azure Database for MariaDB |
| 3 | +description: This article describes the Performance Recommendation feature in Azure Database for MariaDB |
| 4 | +author: ajlam |
| 5 | +ms.author: andrela |
| 6 | +ms.service: mariadb |
| 7 | +ms.topic: conceptual |
| 8 | +ms.date: 06/12/2019 |
| 9 | +--- |
| 10 | +# Performance Recommendations in Azure Database for MariaDB |
| 11 | + |
| 12 | +**Applies to:** Azure Database for MariaDB 10.2s |
| 13 | + |
| 14 | +> [!NOTE] |
| 15 | +> 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. |
| 16 | +
|
| 17 | +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. |
| 18 | + |
| 19 | +## Permissions |
| 20 | + |
| 21 | +**Owner** or **Contributor** permissions required to run analysis using the Performance Recommendations feature. |
| 22 | + |
| 23 | +## Performance recommendations |
| 24 | + |
| 25 | +The [Performance Recommendations](concepts-performance-recommendations.md) feature analyzes workloads across your server to identify indexes with the potential to improve performance. |
| 26 | + |
| 27 | +Open **Performance Recommendations** from the **Intelligent Performance** section of the menu bar on the Azure portal page for your MariaDB server. |
| 28 | + |
| 29 | + |
| 30 | + |
| 31 | +Select **Analyze** and choose a database, which will begin the analysis. Depending on your workload, the analysis may take several minutes to complete. Once the analysis is done, there will be a notification in the portal. Analysis performs a deep examination of your database. We recommend you perform analysis during off-peak periods. |
| 32 | + |
| 33 | +The **Recommendations** window will show a list of recommendations if any were found and the related query ID that generated this recommendation. With the query ID, you can use the [mysql.query_store](concepts-query-store.md#mysqlquery_store) view to learn more about the query. |
| 34 | + |
| 35 | + |
| 36 | + |
| 37 | +Recommendations are not automatically applied. To apply the recommendation, copy the query text and run it from your client of choice. Remember to test and monitor to evaluate the recommendation. |
| 38 | + |
| 39 | +## Recommendation types |
| 40 | + |
| 41 | +Currently, only *Create Index* recommendations are supported. |
| 42 | + |
| 43 | +### Create Index recommendations |
| 44 | + |
| 45 | +*Create Index* recommendations suggest new indexes to speed up the most frequently run or time-consuming queries in the workload. This recommendation type requires [Query Store](concepts-query-store.md) to be enabled. Query Store collects query information and provides the detailed query runtime and frequency statistics that the analysis uses to make the recommendation. |
| 46 | + |
| 47 | +## Next steps |
| 48 | + |
| 49 | +- Learn more about [monitoring and tuning](concepts-monitoring.md) in Azure Database for MariaDB. |
0 commit comments