Merge pull request #36491 from WilliamDAssafMSFT/mstehrani-patch-22

Mstehrani patch 22

Author: prmerger-automator[bot]

docs/relational-databases/system-catalog-views/sys-databases-transact-sql.md

@@ -4,7 +4,7 @@ description: The sys.databases system catalog view contains one row per database
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: wiassaf
-ms.date: 12/10/2025
+ms.date: 01/27/2026
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -112,7 +112,7 @@ If a database isn't `ONLINE`, or `AUTO_CLOSE` is set to `ON` and the database is
 | `catalog_collation_type` | **int** | The catalog collation setting:<br />`0` = DATABASE_DEFAULT<br />`2` = `SQL_Latin_1_General_CP1_CI_AS`<br /><br />**Applies to**: [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] |
 | `catalog_collation_type_desc` | **nvarchar(60)** | The catalog collation setting:<br />DATABASE_DEFAULT<br />`SQL_Latin_1_General_CP1_CI_AS`<br /><br />**Applies to**: [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] |
 | `physical_database_name` | **nvarchar(128)** | For [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], the physical name of the database. For [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], a unique identifier for the current physical database corresponding to the user database. Changing the database service level objective or restoring the database will cause this value to change.<br /><br />**Applies to**: [!INCLUDE [sql-server-2019](../../includes/sssql19-md.md)] and later versions, and [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] |
-| `is_result_set_caching_on` | **bit** | Indicates whether result set caching is enabled.<br />`1` = result set caching is enabled<br />`0` = result set caching is disabled<br /><br />**Applies to**: [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)] dedicated SQL pools and [!INCLUDE [fabric](../../includes/fabric.md)]. For more information, see [Result set caching (preview)](/fabric/data-warehouse/result-set-caching). |
+| `is_result_set_caching_on` | **bit** | Indicates whether result set caching is enabled.<br />`1` = result set caching is enabled<br />`0` = result set caching is disabled<br /><br />**Applies to**: [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)] dedicated SQL pools and [!INCLUDE [fabric-dw](../../includes/fabric-dw.md)]. For more information in [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)], see [Performance tuning with result set caching](/azure/synapse-analytics/sql-data-warehouse/performance-tuning-result-set-caching). For more information in [!INCLUDE [fabric-dw](../../includes/fabric-dw.md)], see [Result set caching](/fabric/data-warehouse/result-set-caching). |
 | `is_accelerated_database_recovery_on` | **bit** | Indicates whether Accelerated Database Recovery (ADR) is enabled.<br />`1` = ADR is enabled<br />`0` = ADR is disabled<br /><br />**Applies to**: [!INCLUDE [sql-server-2019](../../includes/sssql19-md.md)] and later versions, [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], and [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] |
 | `is_tempdb_spill_to_remote_store` | **bit** | Indicates whether `tempdb` spill to remote store is enabled.<br />`1` = enabled<br />`0` = disabled<br /><br />**Applies to**: [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)] Gen2. |
 | `is_stale_page_detection_on` | **bit** | Indicates whether stale page detection is enabled.<br />`1` = stale page detection is enabled<br />`0` = stale page detection is disabled<br /><br />**Applies to**: [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)] Gen2. While this feature is being rolled out to all regions, check the version deployed to your instance and the latest [Azure Synapse release notes](/azure/synapse-analytics/sql-data-warehouse/release-notes-10-0-10106-0) and [Gen2 upgrade schedule](/azure/synapse-analytics/sql-data-warehouse/gen2-migration-schedule) for feature availability. |

docs/t-sql/queries/hints-transact-sql-query.md

@@ -354,7 +354,7 @@ The following hint names are supported:
 | `'FORCE_LEGACY_CARDINALITY_ESTIMATION'` <a id="use_hint_ce70"></a> | Forces the Query Optimizer to use [Cardinality Estimation](../../relational-databases/performance/cardinality-estimation-sql-server.md) model of [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] and earlier versions. This hint name is equivalent to [trace flag](../database-console-commands/dbcc-traceon-trace-flags-transact-sql.md) 9481 or [database scoped configuration](../statements/alter-database-scoped-configuration-transact-sql.md) setting `LEGACY_CARDINALITY_ESTIMATION = ON`. |
 | `'QUERY_OPTIMIZER_COMPATIBILITY_LEVEL_n'` <sup>1</sup> | Forces the Query Optimizer behavior at a query level. This behavior happens as if the query was compiled with database compatibility level *n*, where *n* is a supported database compatibility level. For a list of currently supported values for *n*, see [sys.dm_exec_valid_use_hints](../../relational-databases/system-dynamic-management-views/sys-dm-exec-valid-use-hints-transact-sql.md).<br /><br />**Applies to**: [!INCLUDE [ssSQL17](../../includes/sssql17-md.md)] CU 10 and later versions, and [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] |
 | `'QUERY_PLAN_PROFILE'` <sup>2</sup> | Enables lightweight profiling for the query. When a query that contains this new hint finishes, a new extended event, `query_plan_profile`, is fired. This extended event exposes execution statistics and actual execution plan XML similar to the `query_post_execution_showplan` extended event but only for queries that contains the new hint.<br /><br />**Applies to**: [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] SP 2 CU 3, [!INCLUDE [ssSQL17](../../includes/sssql17-md.md)] CU 11, and later versions |
-| `'DISABLE_RESULT_SET_CACHE'` | Disables result set caching (preview) for a specific run of a query, if result set cache is enabled for the currently connected item. This means it will neither generate new result set cache nor use existing result set cache (if any). This could be useful in debugging or A/B testing scenarios. For more information, see [Result set caching](/fabric/data-warehouse/result-set-caching).<br /><br />**Applies to**: [!INCLUDE [fabric](../../includes/fabric.md)] |
+| `'DISABLE_RESULT_SET_CACHE'` | Disables result set caching for a specific run of a query, if result set cache is enabled for the currently connected item. This means it will neither generate new result set cache nor use existing result set cache (if any). This could be useful in debugging or A/B testing scenarios. For more information, see [Result set caching](/fabric/data-warehouse/result-set-caching).<br /><br />**Applies to**: [!INCLUDE [fabric-dw](../../includes/fabric-dw.md)] |
 
 <sup>1</sup> The `QUERY_OPTIMIZER_COMPATIBILITY_LEVEL_n` hint doesn't override default or legacy cardinality estimation setting, if you force it through database scoped configuration, trace flag, or another query hint such as `QUERYTRACEON`. This hint only affects the behavior of the Query Optimizer. It doesn't affect other features of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] that might depend on the [database compatibility level](../statements/alter-database-transact-sql-compatibility-level.md), such as the availability of certain database features. For more information, see [Developer's Choice: Hinting Query Execution model](/archive/blogs/sql_server_team/developers-choice-hinting-query-execution-model).
 
@@ -797,9 +797,11 @@ FROM FactInternetSales
 OPTION (FORCE DISTRIBUTED PLAN);
 ```
 
-### Q. Disable a query from creating or applying result set cache (preview)
+<a id="q-disable-a-query-from-creating-or-applying-result-set-cache-preview"></a>
 
-**Applies to**: [!INCLUDE [fabric](../../includes/fabric.md)]
+### Q. Disable a query from creating or applying result set cache
+
+**Applies to**: [!INCLUDE [fabric-dw](../../includes/fabric-dw.md)]
 
 Use `'DISABLE_RESULT_SET_CACHE'` as a `hint_name` to block result set cache for a particular run of a query. For more information, see [Result set caching](/fabric/data-warehouse/result-set-caching).
 

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

@@ -4074,7 +4074,7 @@ Updates the timestamp for an existing warehouse snapshot in Fabric Data Warehous
 
 #### RESULT_SET_CACHING
 
-Enables or disables result set caching (preview) for the target item. During preview, the default setting of this feature is `OFF`. For more information, see [Result set caching](/fabric/data-warehouse/result-set-caching).
+Enables or disables result set caching for the target item. The default setting of this feature is `ON`. For more information, see [Result set caching](/fabric/data-warehouse/result-set-caching).
 
 #### PROACTIVE_STATISTICS_REFRESH
 
@@ -4102,15 +4102,17 @@ To check the current status of Delta Lake Log publishing on all warehouses, of y
 SELECT [name], [DATA_LAKE_LOG_PUBLISHING_DESC] FROM sys.databases;
 ```
 
-### B. Set and check result set caching (preview)
+<a id="set-and-check-result-set-caching-preview"></a>
 
-The following T-SQL command will enable the item `MyDataWarehouse` to begin creating and applying result set cache (preview) to applicable `SELECT` queries. For more information, see [Result set caching](/fabric/data-warehouse/result-set-caching).
+### B. Set and check result set caching
+
+The following T-SQL command will enable the item `MyDataWarehouse` to begin creating and applying result set cache to applicable `SELECT` queries. For more information, see [Result set caching](/fabric/data-warehouse/result-set-caching).
 
 ```sql
 ALTER DATABASE [MyDataWarehouse] SET RESULT_SET_CACHING ON;
 ```
 
-The column `is_result_set_caching_on` from [sys.databases](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md?view=fabric&preserve-view=true) can then be checked to confirm that result set caching (preview) has been enabled.
+The column `is_result_set_caching_on` from [sys.databases](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md?view=fabric&preserve-view=true) can then be checked to confirm that result set caching has been enabled.
 
 ```sql
 SELECT [name], [is_result_set_caching_on] FROM sys.databases;