Merge pull request #26110 from thesqlsith/patch-3

Update dbcc-traceon-trace-flags-transact-sql.md

Author: prmerger-automator[bot]

docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md

@@ -130,7 +130,7 @@ Trace flag behavior may not be supported in future releases of [!INCLUDE[ssNoVer
 | <a id="tf2390"></a>**2390** | Enable automatically generated quick statistics for ascending or unknown keys (histogram amendment). If Trace Flag 2390 is set, and a leading statistics column is marked as ascending or unknown, then the histogram used to estimate cardinality will be adjusted at query compile time. For more information, see [KB2801413](https://support.microsoft.com/kb/2801413).<br /><br />**Note:** Ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Note:** This trace flag doesn't apply to CE version 120 or above. Use Trace Flag 4139 instead.<br /><br />**Scope:** Global or session or query (QUERYTRACEON). |
 | <a id="tf2422"></a>**2422** | Enables the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] to abort a request when the maximum time set by Resource Governor REQUEST_MAX_CPU_TIME_SEC configuration is exceeded. For more information, see [KB4038419](https://support.microsoft.com/kb/4038419).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] Service Pack 2, [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU 3, and later.<br /><br />**Scope:** Global only. |
 | <a id="tf2430"></a>**2430** | Enables alternate lock class cleanup. For more information, see [KB2754301](https://support.microsoft.com/kb/2754301).<br /><br />**Scope:** Global only. |
-| <a id="tf2446"></a>**2446** | Causes SQL Server to generate a Showplan XML fragment with the `ParameterRuntimeValue` when using the lightweight query execution statistics profiling infrastructure or executing the `sys.dm_exec_query_statistics_xml` DMV while troubleshooting long running queries.<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU 31, and [!INCLUDE[ssSQL22](../../includes/sssql22-md.md)] and later.<br /><br />**Warning:** Trace Flag 2446 isn't meant to be enabled continuously in a production environment, but only for time-limited troubleshooting purposes. Using this trace flag will introduce additional and possibly significant CPU and memory overhead as we will create a Showplan XML fragment with runtime parameter information, whether the `sys.dm_exec_query_statistics_xml` DMV is called or not.<br /><br />**Note:** Starting with [!INCLUDE[ssSQL22](../../includes/sssql22-md.md)], to accomplish this at the database level see the FORCE_SHOWPLAN_RUNTIME_PARAMETER_COLLECTION option in [ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).<br /><br />**Scope:** Global only. |
+| <a id="tf2446"></a>**2446** | Causes SQL Server to generate a Showplan XML fragment with the `ParameterRuntimeValue` when using the lightweight query execution statistics profiling infrastructure or executing the `sys.dm_exec_query_statistics_xml` DMV while troubleshooting long running queries.<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU 31, [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] CU 19, and [!INCLUDE[ssSQL22](../../includes/sssql22-md.md)] and later.<br /><br />**Warning:** Trace Flag 2446 isn't meant to be enabled continuously in a production environment, but only for time-limited troubleshooting purposes. Using this trace flag will introduce additional and possibly significant CPU and memory overhead as we will create a Showplan XML fragment with runtime parameter information, whether the `sys.dm_exec_query_statistics_xml` DMV is called or not.<br /><br />**Note:** Starting with [!INCLUDE[ssSQL22](../../includes/sssql22-md.md)], to accomplish this at the database level see the FORCE_SHOWPLAN_RUNTIME_PARAMETER_COLLECTION option in [ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).<br /><br />**Scope:** Global only. |
 | <a id="tf2451"></a>**2451** | Enables the equivalent of the last actual execution plan in `sys.dm_exec_query_plan_stats`.<br /><br />**Note:** This trace flag applies to [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] and later.<br /><br />**Note:** Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] to accomplish this at the database level see the LAST_QUERY_PLAN_STATS option in [ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).<br /><br />**Scope:** Global only. |
 | <a id="tf2453"></a>**2453** | Allows a table variable to trigger recompile when enough number of rows are changed. For more information, see [KB2952444](https://support.microsoft.com/kb/2952444).<br /><br />**Note:** Ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope:** Global or session or query (QUERYTRACEON). |
 | <a id="tf2467"></a>**2467** | Enables an alternate parallel worker thread allocation policy, based on which node has the least allocated threads. For more information, see [Parallel Query Processing](../../relational-databases/query-processing-architecture-guide.md#parallel-query-processing). Refer to [Configure the max worker threads Server Configuration Option](../../database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option.md) for information on configuring the max worker threads server option.<br /><br />**Note:** Query degree of parallelism (DOP) has to fit into a single node for this alternate policy to be used, or the default thread allocation policy is used instead. Using this trace flag, it isn't recommended to execute queries specifying a DOP over the number of schedulers in a single node, as this could interfere with queries specifying a DOP below or equal to the number of schedulers in a single node.<br /><br />**Note:** Ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope:** Global only. |
@@ -237,6 +237,7 @@ Trace flag behavior may not be supported in future releases of [!INCLUDE[ssNoVer
 | <a id="tf10204"></a>**10204** | Disables merge/recompress during columnstore index reorganization. In [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)], when a columnstore index is reorganized, there is new functionality to automatically merge any small compressed rowgroups into larger compressed rowgroups, and recompressing any rowgroups that have a large number of deleted rows.<br /><br />**Note:** Trace Flag 10204 doesn't apply to columnstore indexes that are created on memory-optimized tables.<br /><br />**Scope:** Global or session. |
 | <a id="tf10207"></a>**10207** | Allows clustered columnstore index (CCI) scans to skip corrupt segments or metadata, allowing data retrieval from a corrupt CCI. For more information, see [KB3067257](https://support.microsoft.com/kb/3067257).<br /><br />**Scope:** Global or session. |
 | <a id="tf10316"></a>**10316** | Enables creation of additional indexes on [internal memory-optimized staging temporal table](../../relational-databases/tables/system-versioned-temporal-tables-with-memory-optimized-tables.md), beside the default one. If you have specific query pattern that includes columns that aren't covered by the default index, you may consider adding additional indexes.<br /><br />**Note:** System-versioned temporal tables for Memory-Optimized Tables are designed to provide high transactional throughput. Creating additional indexes may introduce overhead for DML operations that update or delete rows in the current table. With the additional indexes you should aim to find the right balance between performance of temporal queries and additional DML overhead.<br /><br />**Scope:** Global or session. |
+| <a id="tf10460"></a>**10460** | Causes the SQL Server Stretch Database feature to provision a stretched table within the Azure SQL Database Hyperscale service tier.<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU 31, [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] CU 18, and [!INCLUDE[ssSQL22](../../includes/sssql22-md.md)] and later.<br /><br />Starting with [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU 31, [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] CU 18, and [!INCLUDE[ssSQL22](../../includes/sssql22-md.md)], the default behavior of the Stretch Database feature will provision a stretched table within an Azure SQL Database Standard service tier (S3). For more information, see [KB5018050](https://support.microsoft.com/topic/kb5018050-improvement-add-new-azure-sql-database-service-tier-options-to-the-stretch-database-feature-00e9bd6e-13be-439c-9878-4d4721f5a197).<br /><br />**Scope:** Global only. |
 | <a id="tf11023"></a>**11023** | Disables the use of the last persisted sample rate for all subsequent statistics update, where a sample rate isn't specified explicitly as part of the [UPDATE STATISTICS](../../t-sql/statements/update-statistics-transact-sql.md) statement. For more information, see [KB4039284](https://support.microsoft.com/kb/4039284).<br /><br />**Scope:** Global only. |
 | <a id="tf11024"></a>**11024** | Enables triggering the auto update of statistics when the modification count of any partition exceeds the local [threshold](../../relational-databases/statistics/statistics.md#auto_update_statistics-option). For more information, see [KB4041811](https://support.microsoft.com/kb/4041811).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] Service Pack 2, [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU 3, and later.<br /><br />**Scope:** Global only. |
 | <a id="tf11047"></a>**11047** | Applies the default timeout set by `query wait (s)` or the Resource Governor `REQUEST_MEMORY_GRANT_TIMEOUT_SEC` configuration to columnstore index build operations. For more information, see [KB4480641](https://support.microsoft.com/kb/4480641).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] Service Pack 2 CU 5, [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU 14, and later.<br /><br />**Scope:** Global only. |
@@ -267,4 +268,4 @@ Trace flag behavior may not be supported in future releases of [!INCLUDE[ssNoVer
 - [ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md)
 - [DBCC TRACEOFF (Transact-SQL)](../../t-sql/database-console-commands/dbcc-traceoff-transact-sql.md)
 - [DBCC TRACEON (Transact-SQL)](../../t-sql/database-console-commands/dbcc-traceon-transact-sql.md)
-- [DBCC TRACESTATUS (Transact-SQL)](../../t-sql/database-console-commands/dbcc-tracestatus-transact-sql.md)
+- [DBCC TRACESTATUS (Transact-SQL)](../../t-sql/database-console-commands/dbcc-tracestatus-transact-sql.md)