|
1 | 1 | # Microsoft SQL Server Trace Flags
|
2 |
| -Complete list of Microsoft SQL Server trace flags (528 trace flags) |
| 2 | +Complete list of Microsoft SQL Server trace flags (529 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.**
|
@@ -64,6 +64,8 @@ Trace Flags are settings that in some way or another alters the behavior of vari
|
64 | 64 |
|
65 | 65 | <a id="how-do-i-know-what-trace-flags-are-turned-on-at-the-moment"></a>
|
66 | 66 | ## How do I know what Trace Flags are turned on at the moment?
|
| 67 | +From SSMS 16 every sql plan content information about trace flags in section `Trace flags` |
| 68 | + |
67 | 69 | You can use the [DBCC TRACESTATUS](https://docs.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-tracestatus-transact-sql "Microsoft Docs DBCC TRACESTATUS") command
|
68 | 70 |
|
69 | 71 | The following example displays the status of all trace flags that are currently enabled globally:
|
@@ -558,11 +560,12 @@ Link: None
|
558 | 560 | <a id="692"></a>
|
559 | 561 | #### Trace Flag: 692
|
560 | 562 | Function: Disables fast inserts while bulk loading data into heap or clustered index.
|
561 |
| -Starting SQL Server 2016, fast inserts is enabled by default leveraging minimal logging when database is in simple or bulk logged recovery model to optimize insert performance for records inserted into new pages. With fast inserts, each bulk load batch acquires new extent(s) bypassing the allocation lookup for existing extent with available free space to optimize insert performance. |
562 |
| -With fast inserts, bulk loads with small batch sizes can lead to increased unused space consumed by objects hence it is recommended to use large batchsize for each batch to fill the extent completely. If increasing batchsize is not feasible, this trace flag can help reduce unused space reserved at the expense of performance.<br /> |
| 563 | +Starting SQL Server 2016, fast inserts is enabled by default leveraging minimal logging when database is in simple or bulk logged recovery model to optimize insert performance for records inserted into new pages. |
| 564 | +With fast inserts, each bulk load batch acquires new extent(s) bypassing the allocation lookup for existing extent with available free space to optimize insert performance. |
| 565 | +With fast inserts, bulk loads with small batch sizes can lead to increased unused space consumed by objects hence it is recommended to use large batch size for each batch to fill the extent completely. |
| 566 | +If increasing batch size is not feasible, this trace flag can help reduce unused space reserved at the expense of performance.<br /> |
563 | 567 | **Note: This trace flag applies to SQL Server 2016 RTM and higher builds.**
|
564 | 568 | Link: https://blogs.msdn.microsoft.com/sql_server_team/sql-server-2016-minimal-logging-and-impact-of-the-batchsize-in-bulk-load-operations/<br />
|
565 |
| -Link: <br /> |
566 | 569 | Scope: global or session
|
567 | 570 |
|
568 | 571 |
|
@@ -2421,9 +2424,13 @@ Link: https://support.microsoft.com/en-us/help/958006/fix-the-size-of-the-sql-se
|
2421 | 2424 |
|
2422 | 2425 | <a id="4134"></a>
|
2423 | 2426 | #### Trace Flag: 4134
|
2424 |
| -Function: Bugfix for error: parallel query returning different results every time<br /> |
| 2427 | +Function: Bugfix for error: parallel query returning different results every time |
| 2428 | + The trace flag disables an optimization in the query optimizer. |
| 2429 | +The optimization caused the issue described in the KB article when you try to insert into a table by selecting from the table itself. |
| 2430 | +As turning on the trace flag could result in a perf degradation, you only should use it if you run into the issue described in the KB article.<br /> |
2425 | 2431 | Link: http://support.microsoft.com/kb/2546901<br />
|
2426 |
| -Link: http://sql-sasquatch.blogspot.se/2014/04/whaddayaknow-bout-sqlserver-trace-flag.html |
| 2432 | +Link: http://sql-sasquatch.blogspot.se/2014/04/whaddayaknow-bout-sqlserver-trace-flag.html<br /> |
| 2433 | +Link: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9ea718c2-e0e0-40cf-b12b-3269130448b7/trace-flag-4135-sql-server-2008?forum=sqldatabaseengine |
2427 | 2434 |
|
2428 | 2435 |
|
2429 | 2436 | <a id="4135"></a>
|
@@ -3742,6 +3749,13 @@ Link: https://support.microsoft.com/en-us/help/3142595/fix-an-access-violation-o
|
3742 | 3749 | Link: https://support.microsoft.com/en-us/help/3138659/fix-slow-performance-when-you-query-numeric-data-types-from-an-oracle-database
|
3743 | 3750 |
|
3744 | 3751 |
|
| 3752 | +<a id="9448"></a> |
| 3753 | +#### Trace Flag: 9448 |
| 3754 | +**Undocumented trace flag**<br /> |
| 3755 | +Function: Disables the referential integrity operator.<br /> |
| 3756 | +Link: https://orderbyselectnull.com/2017/12/05/the-referential-integrity-operator/<br /> |
| 3757 | + |
| 3758 | + |
3745 | 3759 | <a id="9453"></a>
|
3746 | 3760 | #### Trace Flag: 9453
|
3747 | 3761 | Function: Disables Batch Mode in Parallel Columnstore query plans.
|
|
0 commit comments