|**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](http://support.microsoft.com/help/4038419).<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP2, [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU3, and higher builds.<br /><br />**Scope**: global|

|**2430**|Enables alternate lock class cleanup. For more information, see this [Microsoft Support article](http://support.microsoft.com/kb/2754301).<br /><br />**Scope**: global only|

|**2453**|Allows a table variable to trigger recompile when enough number of rows are changed. For more information, see this [Microsoft Support article](http://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|

|**2469**|Enables alternate exchange for `INSERT INTO ... SELECT` into a partitioned columnstore index. For more information, see this [Microsoft Support article](http://support.microsoft.com/kb/3204769).<br /><br />**Scope**: global or session or query|

|**2528**|Disables parallel checking of objects by DBCC CHECKDB, DBCC CHECKFILEGROUP, and DBCC CHECKTABLE. By default, the degree of parallelism is automatically determined by the query processor. The maximum degree of parallelism is configured just like that of parallel queries. For more information, see [Configure the max degree of parallelism Server Configuration Option](../../database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option.md).<br /><br />**Note:** Parallel DBCC checks should typically be enabled (default). The query processor reevaluates and automatically adjusts parallelism for each table or batch of tables checked by DBCC CHECKDB.<br /><br />The typical use scenario is when a system administrator knows that server load will increase before DBCC CHECKDB completes, and so chooses to manually decrease or disable parallelism, in order to increase concurrency with other user workload. However, disabling parallel checks in DBCC CHECKDB can cause it to take longer to complete.<br /><br />**Note:** If DBCC CHECKDB is executed using the TABLOCK option and parallelism is disabled, tables may be locked for longer periods of time.<br /><br />**Note:** Starting with [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] SP2, a MAXDOP option is available to override the max degree of parallelism configuration option of sp_configure for the statement.<br /><br />**Scope**: global or session|

|**2549**|Runs the DBCC CHECKDB command assuming each database file is on a unique disk drive. DBCC CHECKDB command builds an internal list of pages to read per unique disk drive across all database files. This logic determines unique disk drives based on the drive letter of the physical file name of each file.<br /><br />**Note:** Do not use this trace flag unless you know that each file is based on a unique physical disk.<br /><br />**Note:** Although this trace flag improve the performance of the DBCC CHECKDB commands which target usage of the PHYSICAL_ONLY option, some users may not see any improvement in performance. While this trace flag improves disk I/O resources usage, the underlying performance of disk resources may limit the overall performance of the DBCC CHECKDB command. For more information, see this [Microsoft Support article](http://support.microsoft.com/kb/2634571).<br /><br />**Scope**: global only|