article 1

Author: XiaoyuMSFT

articles/sql-data-warehouse/performance-tuning-result-set-caching.md

@@ -1,6 +1,6 @@
 ---
 title: Performance tuning with result set caching 
-description: Result set caching feature overview for Azure SQL Data Warehouse 
+description: Result set caching feature overview for SQL Analytics in Azure Synapse Analytics 
 services: sql-data-warehouse
 author: XiaoyuMSFT
 manager: craigg 
@@ -10,11 +10,11 @@ ms.subservice: development
 ms.date: 10/10/2019
 ms.author: xiaoyul
 ms.reviewer: nidejaco;
-ms.custom: seo-lt-2019  
+ms.custom: azure-synapse
 ---
 
 # Performance tuning with result set caching  
-When result set caching is enabled, Azure SQL Data Warehouse automatically caches query results in the user database for repetitive use.  This allows subsequent query executions to get results directly from the persisted cache so recomputation is not needed.   Result set caching improves query performance and reduces compute resource usage.  In addition, queries using cached results set do not use any concurrency slots and thus do not count against existing concurrency limits. For security, users can only access the cached results if they have the same data access permissions as the users creating the cached results.  
+When result set caching is enabled, SQL Analytics automatically caches query results in the user database for repetitive use.  This allows subsequent query executions to get results directly from the persisted cache so recomputation is not needed.   Result set caching improves query performance and reduces compute resource usage.  In addition, queries using cached results set do not use any concurrency slots and thus do not count against existing concurrency limits. For security, users can only access the cached results if they have the same data access permissions as the users creating the cached results.  
 
 ## Key commands
 [Turn ON/OFF result set caching for a user database](https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-set-options?view=azure-sqldw-latest)
@@ -34,7 +34,7 @@ Once result set caching is turned ON for a database, results are cached for all
 - Queries returning data with row size larger than 64KB
 
 > [!IMPORTANT]
-> The operations to create result set cache and retrieve data from the cache happen on the control node of a data warehouse instance. 
+> The operations to create result set cache and retrieve data from the cache happen on the control node of a SQL Analytics instance.
 > When result set caching is turned ON, running queries that return large result set (for example, >1 million rows) can cause high CPU usage on the control node and slow down the overall query response on the instance.  Those queries are commonly used during data exploration or ETL operations. To avoid stressing the control node and cause performance issue, users should turn OFF result set caching on the database before running those types of queries.  
 
 Run this query for the time taken by result set caching operations for a query:
@@ -71,7 +71,7 @@ WHERE request_id = <'Your_Query_Request_ID'>
 
 The maximum size of result set cache is 1 TB per database.  The cached results are automatically invalidated when the underlying query data change.  
 
-The cache eviction is managed by Azure SQL Data Warehouse automatically following this schedule: 
+The cache eviction is managed by SQL Analytics automatically following this schedule: 
 - Every 48 hours if the result set hasn't been used or has been invalidated. 
 - When the result set cache approaches the maximum size.
 
@@ -82,4 +82,4 @@ Users can manually empty the entire result set cache by using one of these optio
 Pausing a database won't empty cached result set.  
 
 ## Next steps
-For more development tips, see [SQL Data Warehouse development overview](sql-data-warehouse-overview-develop.md). 
+For more development tips, see [development overview](sql-data-warehouse-overview-develop.md).