DBCC TRACEON (Transact-SQL)
Applies To: SQL Server 2014, SQL Server 2016 Preview
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
Enables the specified trace flags.
Applies to: SQL Server (SQL Server 2008 through current version).
On a production server, to avoid unpredictable behavior, we recommend that you only enable trace flags server-wide by using one of the following methods:
Use the -T command-line startup option of Sqlservr.exe. This is a recommended best practice because it makes sure that all statements will run with the trace flag enabled. These include commands in startup scripts. For more information, see sqlservr Application.
Use DBCC TRACEON ( trace# [, ....n], -1 ) only while users or applications are not concurrently running statements on the system.
Trace flags are used to customize certain characteristics by controlling how SQL Server operates. Trace flags, after they are enabled, remain enabled in the server until disabled by executing a DBCC TRACEOFF statement. In SQL Server, there are two types of trace flags: session and global. Session trace flags are active for a connection and are visible only for that connection. Global trace flags are set at the server level and are visible to every connection on the server. To determine the status of trace flags, use DBCC TRACESTATUS. To disable trace flags, use DBCC TRACEOFF.
DBCC TRACEON returns the following result set (message):
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
The following example disables hardware compression for tape drivers, by switching on trace flag 3205. This flag is switched on only for the current connection.
The following example switches on trace flag 3205 globally.
The following example switches on trace flags 3205, and 260 globally.