|
1 | 1 | # Microsoft SQL Server Trace Flags |
2 | | -Complete list of Microsoft SQL Server trace flags (531 trace flags) |
| 2 | +Complete list of Microsoft SQL Server trace flags (532 trace flags) |
3 | 3 |
|
4 | 4 | **REMEMBER: Be extremely careful with trace flags, test in your test environment first. And consult professionals first if you are the slightest uncertain about the effects of your changes.** |
5 | 5 | **Trace flag behavior may not be supported in future releases of SQL Server.** |
@@ -172,7 +172,7 @@ Use this trace flag if SQL Server is experiencing high number of QDS_LOADDB wait |
172 | 172 |
|
173 | 173 | <a id="trace-flags-list"></a> |
174 | 174 | ## Trace Flags List |
175 | | -Summary: **531 trace flags** |
| 175 | +Summary: **532 trace flags** |
176 | 176 |
|
177 | 177 |
|
178 | 178 | <a id="-1"></a> |
@@ -1364,6 +1364,14 @@ Function: Another one I stumbled upon myself...outputs info about "Smart Seek |
1364 | 1364 | Link: None |
1365 | 1365 |
|
1366 | 1366 |
|
| 1367 | +<a id="2422"></a> |
| 1368 | +#### Trace Flag: 2422 |
| 1369 | +Function: Enables the SQL Server Database Engine to abort a request when the maximum time set by Resource Governor REQUEST_MAX_CPU_TIME_SEC configuration is exceeded.<br /> |
| 1370 | +**Note: This trace flag applies to SQL Server 2017 CU3 and higher builds.** |
| 1371 | +Link: http://support.microsoft.com/help/4038419<br /> |
| 1372 | +Scope: global only |
| 1373 | + |
| 1374 | + |
1367 | 1375 | <a id="2430"></a> |
1368 | 1376 | #### Trace Flag: 2430 |
1369 | 1377 | Function: Fixes performance problem when using large numbers of locks<br /> |
|
0 commit comments