Merge pull request #23821 from thesqlsith/patch-6

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

@@ -120,7 +120,8 @@ The following table lists and describes the trace flags that are available in [!
 |<a name="tf2389"></a>**2389**|Enable automatically generated quick statistics for ascending keys (histogram amendment). If trace flag 2389 is set, and a leading statistics column is marked as ascending, then the histogram used to estimate cardinality will be adjusted at query compile time. <br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Note:** This trace flag does not apply to CE version 120 or above. Use trace flag 4139 instead.<br /><br />**Scope**: global or session or query (QUERYTRACEON)|
 |<a name="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 this [Microsoft Support article](https://support.microsoft.com/kb/2801413).<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Note:** This trace flag does not apply to CE version 120 or above. Use trace flag 4139 instead.<br /><br />**Scope**: global or session or query (QUERYTRACEON)|
 |<a name="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 this [Microsoft Support article](https://support.microsoft.com/help/4038419).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] SP2, [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU3, and higher builds.<br /><br />**Scope**: global|
-|<a name="tf2430"></a>**2430**|Enables alternate lock class cleanup. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/2754301).<br /><br />**Scope**: global only| 
+|<a name="tf2430"></a>**2430**|Enables alternate lock class cleanup. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/2754301).<br /><br />**Scope**: global only|
+|<a name="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 DMV while troubleshooting long running queries.<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU31. <br /><br />**WARNING:** Trace flag 2446 is not 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 />**Scope**: global only|   
 |<a name="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 higher builds.<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 &#40;Transact-SQL&#41;](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).<br /><br />**Scope**: global only|  
 |<a name="tf2453"></a>**2453**|Allows a table variable to trigger recompile when enough number of rows are changed. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/2952444).<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope**: global or session or query (QUERYTRACEON)|
 |<a name="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 is not 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:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope**: global only|