Merge pull request #9825 from pmasl/patch-531

Update query-store-usage-scenarios.md

Author: PRMerger14

docs/relational-databases/performance/query-store-usage-scenarios.md

@@ -125,6 +125,9 @@ Starting with [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] all Query Optimi
     a.  For cases where there are regressions, force the previously known good plan in the Query Store.  
 
     b.  If there are query plans that fail to force, or if performance is still insufficient, consider reverting the [database compatibility level](../../relational-databases/databases/view-or-change-the-compatibility-level-of-a-database.md) to the prior setting, and then engaging Microsoft Customer Support.  
+    
+> [!TIP]
+> Use [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] *Upgrade Database* task to upgrade the [database compatibility level](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md#compatibility-levels-and-sql-server-upgrades) of the database. See [Upgrading Databases by using the Query Tuning Assistant](../../relational-databases/performance/upgrade-dbcompat-using-qta.md) for details.
   
 ## Identify and improve ad hoc workloads  
 Some workloads do not have dominant queries that you can tune to improve overall application performance. Those workloads are typically characterized with relatively large number of different queries each of them consuming portion of system resources. Being unique, those queries are executed very rarely (usually only once, thus name ad hoc), so their runtime consumption is not critical. On the other hand, given that application is generating net new queries all the time, significant portion of system resources is spent on query compilation, which is not optimal. This is not ideal situation for Query Store either given that large number of queries and plans flood the space you have reserved which means that Query Store will likely end up in the read-only mode very quickly. If you activated **Size Based Cleanup Policy** ([highly recommended](best-practice-with-the-query-store.md) to keep Query Store always up and running), then background process will be cleaning Query Store structures most of the time also taking significant system resources.  
@@ -211,6 +214,7 @@ ALTER DATABASE [QueryStoreTest] SET QUERY_STORE = ON
 
 ## See Also  
  [Monitoring Performance By Using the Query Store](../../relational-databases/performance/monitoring-performance-by-using-the-query-store.md)   
- [Best Practice with the Query Store](../../relational-databases/performance/best-practice-with-the-query-store.md)  
+ [Best Practice with the Query Store](../../relational-databases/performance/best-practice-with-the-query-store.md)         
+ [Upgrading Databases by using the Query Tuning Assistant](../../relational-databases/performance/upgrade-dbcompat-using-qta.md)