Merge pull request #23530 from mstehrani/patch-12

Note on decryptbykey

Author: PRMerger8

docs/t-sql/statements/alter-database-transact-sql-set-options.md

@@ -3345,6 +3345,8 @@ Disables the Query Store. OFF is the default value.
 
 Controls whether query result is cached in the database.
 
+
+
 #### RESULT_SET_CACHING { ON | OFF}     
 
 ON     
@@ -3369,6 +3371,9 @@ SELECT request_id, command, result_cache_hit FROM sys.dm_pdw_exec_requests
 WHERE request_id = <'Your_Query_Request_ID'>
 ```
 
+> [!NOTE]
+> Result set caching should not be used in conjunction with [DECRYPTBYKEY](/sql/t-sql/functions/decryptbykey-transact-sql). If this cryptographic function must be used, ensure you have result set caching disabled (either at [session-level](/sql/t-sql/statements/set-result-set-caching-transact-sql) or [database-level](/sql/t-sql/statements/alter-database-transact-sql-set-options)) at the time of execution.
+
 > [!IMPORTANT]
 > The operations to create result set cache and retrieve data from the cache happen on the control node of a data warehouse 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.  
 
@@ -3450,4 +3455,4 @@ SET READ_COMMITTED_SNAPSHOT ON;
 - [Best practices for Azure Synapse Analytics](/azure/sql-data-warehouse/sql-data-warehouse-best-practices#maintain-statistics)
 - [Designing tables in Azure Synapse Analytics](/azure/sql-data-warehouse/sql-data-warehouse-tables-overview#statistics)
 
-::: moniker-end
+::: moniker-end