Skip to content

Commit 8ee2023

Browse files
committed
Learn Editor: Update dbcc-traceon-trace-flags-transact-sql.md
1 parent 5266f47 commit 8ee2023

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ Trace flag behavior might not be supported in future releases of [!INCLUDE [ssNo
8888
| Trace flag | Description |
8989
| --- | --- |
9090
| <a id="tf101"></a>**101** | Increases the verboseness of the merge replication agent logging.<br /><br />**Important:** Trace Flag 101 can only be enabled for the [Replication Merge Agent](../../relational-databases/replication/agents/replication-merge-agent.md) using the `-T` option when executing **replmerg.exe** from the command prompt.<br /><br />**Warning:** Trace Flag 101 isn't meant to be enabled continuously in a production environment, but only for time-limited troubleshooting purposes. For more information, see [Find errors with the Merge Agent](../../relational-databases/replication/troubleshoot-tran-repl-errors.md#find-errors-with-the-merge-agent).<br /><br />**Scope:** Replication Merge Agent only. |
91-
| <a id="tf102"></a>**102** | Increases the verboseness of the merge replication agent logging and directs it to the *\<Distribution server>..msmerge_history* table.<br /><br />**Important:** Trace Flag 102 can only be enabled for the [Replication Merge Agent](../../relational-databases/replication/agents/replication-merge-agent.md) using the `-T` option when executing **replmerg.exe** from the command prompt.<br /><br />**Warning:** Trace Flag 102 isn't meant to be enabled continuously in a production environment, but only for time-limited troubleshooting purposes. For more information, see [Find errors with the Merge Agent](../../relational-databases/replication/troubleshoot-tran-repl-errors.md#find-errors-with-the-merge-agent).<br /><br />**Scope:** Replication Merge Agent only. |
91+
| <a id="tf102"></a>**102** | Increases the verboseness of the merge replication agent logging and directs it to the *<Distribution server>..msmerge_history* table.<br /><br />**Important:** Trace Flag 102 can only be enabled for the [Replication Merge Agent](../../relational-databases/replication/agents/replication-merge-agent.md) using the `-T` option when executing **replmerg.exe** from the command prompt.<br /><br />**Warning:** Trace Flag 102 isn't meant to be enabled continuously in a production environment, but only for time-limited troubleshooting purposes. For more information, see [Find errors with the Merge Agent](../../relational-databases/replication/troubleshoot-tran-repl-errors.md#find-errors-with-the-merge-agent).<br /><br />**Scope:** Replication Merge Agent only. |
9292
| <a id="tf139"></a>**139** | Forces correct conversion semantics in the scope of DBCC check commands like [DBCC CHECKDB](dbcc-checkdb-transact-sql.md), [DBCC CHECKTABLE](dbcc-checktable-transact-sql.md) and [DBCC CHECKCONSTRAINTS](dbcc-checkconstraints-transact-sql.md), when analyzing the improved precision and conversion logic introduced with compatibility level 130 for specific data types, on a database that has a lower compatibility level. For more information, see [SQL Server and Azure SQL Database improvements in handling some data types and uncommon operations](/troubleshoot/sql/database-engine/general/sql-server-azure-sql-database-improvements).<br /><br />**Applies to:** [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] RTM CU 3, [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] Service Pack 1 and later versions.<br /><br />**Warning:** Trace Flag 139 isn't meant to be enabled continuously in a production environment, and should be used for the sole purpose of performing database validation checks described in [SQL Server and Azure SQL Database improvements in handling some data types and uncommon operations](/troubleshoot/sql/database-engine/general/sql-server-azure-sql-database-improvements). It should be immediately disabled after validation checks are completed.<br /><br />**Scope:** Global only. |
9393
| <a id="tf174"></a>**174** | Increases the [!INCLUDE [ssDEnoversion](../../includes/ssdenoversion-md.md)] plan cache bucket count from 40,009 to 160,001 on 64-bit systems. For more information, see [KB3026083](https://support.microsoft.com/kb/3026083).<br /><br />**Note:** Ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope:** Global only. |
9494
| <a id="tf176"></a>**176** | Addresses errors when rebuilding partitions online for tables that contain a computed partitioning column. For more information, see [KB3213683](https://support.microsoft.com/kb/3213683) and [KB4541096](https://support.microsoft.com/kb/4541096).<br /><br />**Scope:** Global or session. |
@@ -152,7 +152,7 @@ Trace flag behavior might not be supported in future releases of [!INCLUDE [ssNo
152152
| <a id="tf2592"></a>**2592** | Enables symbol resolution on stack dumps when the *Debugging Tools for Windows* are installed. For example, using Trace Flag 3656 requires that Trace Flag 2592 is enabled.<br /><br />**Warning:** This is a debugging trace flag and not meant for production environment use.<br /><br />**Applies to:** [!INCLUDE [sql-server-2019](../../includes/sssql19-md.md)] and later versions.<br /><br />**Scope:** Global and session. |
153153
| <a id="tf2610"></a>**2610** | Enables memory dump compression and faster dump generation with **SQLDumper** and via `DBCC STACKDUMP`. For more information, see [Use the Sqldumper.exe utility to generate a dump file in SQL Server](/troubleshoot/sql/tools/use-sqldumper-generate-dump-file#parallel-compression-of-memory-dumps).<br /><br />**Applies to:** [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] CU 8, [!INCLUDE [sql-server-2019](../../includes/sssql19-md.md)] CU 23, and later versions.<br /><br />**Scope:** Global and session. |
154154
| <a id="tf2616"></a>**2616** | Enables the stack signature feature to make **Sqldumper.exe** generate a single dump per unique stack signature per hour, which avoids potential dump flooding problems when the same issue repeats frequently within one hour.<br /><br />When this trace flag is enabled, the format of the dump file will be changed from `SQLDump<xxxx>.mdmp` or `SQLDmpr<xxxx>.mdmp` to `SQLDmpr<xxxx>.P<xxxxx.xxxxxxxx>.T<xxxxxxxxxxxxxx>.{<xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx>}.dmp` (for example, `SQLDmpr0024.P26900.66D498FA.T20240117034050.{eec59a9e-d615-4ac4-a46a-f650fee23787}.dmp`).<br /><br />**Applies to:** [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] CU 12 and later versions.<br /><br />**Scope:** Global only. |
155-
|<a id="tf3012"></a>**3012**| Enables [writing backups to Azure immutable storage](../../relational-databases/backup-restore/sql-server-backup-to-url.md#azure-immutable-storage-support). <br /><br />**Applies to:** [!INCLUDE [ssSQL25](../../includes/sssql25-md.md)] and later versions.<br /><br />**Scope:** Global only.|
155+
|<a id="tf3012"></a>**3012**| Enables [writing backups to Azure immutable storage](../../relational-databases/backup-restore/sql-server-backup-to-url.md#azure-immutable-storage-support). <br /><br />**Applies to:** [!INCLUDE [ssSQL25](../../includes/sssql25-md.md)] and later versions.<br /><br />**Scope:** Global only.|
156156
| <a id="tf3023"></a>**3023** | Enables CHECKSUM option as default for BACKUP command.<br /><br />**Note:** Starting with [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)], this behavior is controlled by setting the **backup checksum default** configuration option. For more information, see [backup checksum default](../../database-engine/configure-windows/backup-checksum-default.md) and [Server configuration options](../../database-engine/configure-windows/server-configuration-options-sql-server.md).<br /><br />**Scope:** Global and session. |
157157
| <a id="tf3042"></a>**3042** | Bypasses the default backup compression preallocation algorithm to allow the backup file to grow only as needed to reach its final size. This trace flag is useful if you need to save on space by allocating only the actual size required for the compressed backup. Using this trace flag might cause a slight performance penalty (a possible increase in the duration of the backup operation). For more information about the preallocation algorithm, see [Backup compression (SQL Server)](../../relational-databases/backup-restore/backup-compression-sql-server.md).<br /><br />**Scope:** Global only. |
158158
| <a id="tf3051"></a>**3051** | Enables [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Backup to URL logging for page blobs in Azure Storage only. Logging writes to a specific error log file. For more information, see [SQL Server Backup to URL Best Practices and Troubleshooting](../../relational-databases/backup-restore/sql-server-backup-to-url-best-practices-and-troubleshooting.md#troubleshooting-backup-to-or-restore-from-url).<br /><br />**Scope:** Global only. |
@@ -282,7 +282,7 @@ Trace flag behavior might not be supported in future releases of [!INCLUDE [ssNo
282282
| <a id="tf11561"></a>**11561** | Disables Microsoft Entra authentication for replication.<br /><br />**Note:** This trace flag applies to [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] CU 6 and later versions.<br /><br />**Scope:** Global or session. |
283283
| <a id="tf11631"></a>**11631** | An `ALTER INDEX ... REORGANIZE` and the [background merge task](../../relational-databases/indexes/columnstore-indexes-overview.md#bckmergetsk) clean up the deleted rows in a columnstore index rowgroup only when a certain threshold of rows has been deleted from that rowgroup. The default threshold is 10% of the maximum row limit (1 million), or of 100,000 rows.<br /><br />This trace flag changes the threshold to 10% of the total current rows in a columnstore rowgroup. For example, if a rowgroup contains 20,000 rows, the threshold is 2,000 deleted rows before this rowgroup is considered for cleanup. For more information, see [KB5000895](https://support.microsoft.com/kb/5000895).<br /><br />**Applies to:** [!INCLUDE [sql-server-2019](../../includes/sssql19-md.md)] CU 9 and later versions.<br /><br />**Scope:** Global only. |
284284
| <a id="tf11634"></a>**11634** | An `ALTER INDEX ... REORGANIZE` and the [background merge task](../../relational-databases/indexes/columnstore-indexes-overview.md#bckmergetsk) clean up the deleted rows in a columnstore index rowgroup only when a certain threshold of rows has been deleted from that rowgroup. The default threshold is 10% of the maximum row limit (1 million), or of 100,000 rows.<br /><br />This trace flag changes the threshold to 1% of the total current rows in a columnstore rowgroup. If enabled together with Trace Flag 11631, then it's 1% of the current number of rows in a rowgroup, instead of 1% of 1 million rows. For more information, see [KB5000895](https://support.microsoft.com/kb/5000895).<br /><br />**Applies to:** [!INCLUDE [sql-server-2019](../../includes/sssql19-md.md)] CU 9 and later versions.<br /><br />**Scope:** Global only. |
285-
| <a id="tf11953"></a>**11953** | Enables you to add Microsoft Entra ID users via the `WITH SID = <sid>, TYPE = [E|X]` syntax in the `CREATE USER` statement.<br /><br />**Note**: Customers must validate Microsoft Entra ID users, because [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] doesn't perform this validation. Consequently, [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] doesn't require any [Microsoft Graph permissions](/azure/azure-sql/virtual-machines/windows/configure-azure-ad-authentication-for-sql-vm#grant-permissions). For more information, see [CREATE USER](../statements/create-user-transact-sql.md#syntax).<br /><br />**Applies to:** [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] CU 20 and later versions.<br /><br />**Scope:** Global only. |
285+
| <a id="tf11953"></a>**11953** | Enables you to add Microsoft Entra ID users via the `WITH SID = <sid>, TYPE = [|X]` syntax in the `CREATE USER` statement.<br /><br />**Note**: Customers must validate Microsoft Entra ID users, because [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] doesn't perform this validation. Consequently, [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] doesn't require any [Microsoft Graph permissions](/azure/azure-sql/virtual-machines/windows/configure-azure-ad-authentication-for-sql-vm#grant-permissions). For more information, see [CREATE USER](../statements/create-user-transact-sql.md#syntax).<br /><br />**Applies to:** [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] CU 20 and later versions.<br /><br />**Scope:** Global only. |
286286
| <a id="tf12310"></a>**12310** | Increases the flow control limits for the number of messages that each availability group gate allows. These limits are the new default values in [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] and therefore the trace flag has no effect in this version. For more information, see [Flow control gates](../../database-engine/availability-groups/windows/monitor-performance-for-always-on-availability-groups.md#flow-control-gates).<br /><br />**Applies to:** [!INCLUDE [ssSQL19-md](../../includes/sssql19-md.md)] CU9, [!INCLUDE [ssSQL17](../../includes/sssql17-md.md)] CU 18, [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] SP 1 CU 16, and later versions.<br /><br />**Scope:** Global only. |
287287
| <a id="tf12324"></a>**12324** | Resolves an issue introduced with changes to the link feature for Azure SQL Managed Instance, which prevents availability groups from synchronizing when replicas are running on different cumulative updates. For more information, see [KB5024276](/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate20).<br /><br />**Applies to:** [!INCLUDE [ssSQL19-md](../../includes/sssql19-md.md)] CU 20 and later versions.<br /><br />**Scope:** Global only. |
288288
| <a id="tf12348"></a>**12348** | Disables the [asynchronous page request dispatching feature](../../database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups.md#asynchronous-page-request-dispatching-improvement) that improves failover when encountering undo-of-redo delays from network latency. Enabling the trace flag reverts the mechanism to the default behavior. <br /><br />**Applies to:** [!INCLUDE [ssSQL25](../../includes/sssql25-md.md)]<br /><br />**Scope:** Global only. |
@@ -293,7 +293,7 @@ Trace flag behavior might not be supported in future releases of [!INCLUDE [ssNo
293293
| <a id="tf13116"></a>**13116** | Disables the fix for bug [13685819](/troubleshoot/sql/releases/sqlserver-2016/servicepack2-cumulativeupdate16). Use this trace flag if after you apply [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] Service Pack 2 CU 16, you encounter an issue in which DML (insert/update/delete) queries that use parallel plans can't complete any execution and encounter HP_SPOOL_BARRIER waits.<br /><br />**Applies to:** [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] Service Pack 2 CU 16.<br /><br />**Scope:** Global only. |
294294
| <a id="tf13127"></a>**13127** | Enables additional string pattern matching optimizations.<br /><br />**Applies to:** [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] and later versions and is intended for high-end systems with high performance workloads.<br /><br />**Scope:** Global or session. |
295295
| <a id="tf13156"></a>**13156** | Disables the fix for the "UDF invocation with a large number of scalar expression re-evaluations can cause a non-yielding scheduler error" issue. This original fix might sometimes cause a performance regression. For more information, see [KB4538581](https://support.microsoft.com/kb/4538581).<br /><br />**Scope:** Global only. |
296-
| <a id="tf13702"></a>**13702** | Enables PolyBase capabilities for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] on Linux. This trace flag also enables other trace flags required to support the PolyBase feature.<br /><br />**Applies to:** [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later versions on Linux.<br /><br />**Scope:** Global only. |
296+
| <a id="tf13702"></a>**13702** | Enables PolyBase capabilities for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] on Linux. This trace flag also enables other trace flags required to support the PolyBase feature. <br /><br />**Applies to:** [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] on Linux.<br /><br />**Scope:** Global only. |
297297
| <a id="tf15025"></a>**15025** | Disables the Azure Key Vault access that is required for a newly created Virtual Log File (VLF), which allows high-volume customer workloads to continue without interruption. Once this trace flag is enabled, [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] uses Extensible Key Management for encryption and key generation, and doesn't contact Azure Key Vault during the creation of the VLF. For more information, see [FIX: Database accessibility issues with high-volume customer workloads that use EKM for encryption and key generation](/troubleshoot/sql/releases/sqlserver-2022/database-accessibility-issues-high-volume-customer-workloads).<br /><br />**Applies to:** [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] CU 19, [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] CU 1, and later versions.<br /><br />**Scope:** Global only. |
298298
| <a id="tf15096"></a>**15096** | Disable population count (popcnt) operations with AVX-512 instruction sets.<br /><br />**Applies to:** [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later versions.<br /><br />**Scope:** Global or session. |
299299
| <a id="tf15097"></a>**15097** | Enables AVX-512 support for [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later versions.<br /><br />**Important:** We recommend enabling AVX-512 support for the following CPUs:<br /><br />- Intel Ice Lake and later<br />- AMD EYPC Genoa and later<br /><br />**Applies to:** [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] and later versions.<br /><br />**Scope:** Global or session. |

0 commit comments

Comments
 (0)