In this post, I am sharing a SQL DBA Script for getting the definition of default trace of SQL Server.

Why is this important?

When you are running multiple traces on your SQL Server while troubleshooting particular event, you should know the definition of the particular trace which helps you in the better investigation.

Using fn_trace_geteventinfo, you can get the trace definition.

Get the default trace_id of instance:

SELECT distinct traceid 
FROM ::fn_trace_getinfo(default)
GO

traceid
-----------
1

Pass trace_id in fn_trace_geteventinfo() and get the definition of Trace:

select
	tg.eventid as EventID
	,te.Name as EventName 
	,tg.columnid as ColumnID
	,cols. name as ColumnName
from :: fn_trace_geteventinfo (1) as tg 
INNER JOIN sys.trace_events as te 
	ON tg.eventid = te.trace_event_id
INNER JOIN sys.trace_columns cols 
	ON tg.columnid = cols.trace_column_id

In this post, I am sharing some of the important Trace Flag of the SQL Server.

Trace flags are frequently used to debug stored procedures and diagnose performance issues.

There are two types of Trace Flag, you can enable particular trace Globally and Session Specific.

You can also visit this article, How to enable and disable default trace of SQL Server.

Enable or Disable Trace Flag for Session:

DBCC TRACEON (TraceNumber)
DBCC TRACEOFF (TraceNumber)

Enable or Disable Trace Flag for Globally:

DBCC TRACEON (TraceNumber,-1)
DBCC TRACEOFF (TraceNumber,-1)

Example:

DBCC TRACEON (3205)

Trace Flag 1222:
Write the information about resources and types of locks in an XML format.

Trace Flag 1204:
Write the information about the deadlock in a text format.

Trace Flag 7806:
Enables a dedicated administrator connection on SQL Server Express Edition.

Trace Flag 1806:
You can disable the instant file initialization.

Trace Flag 4616:
The Application can access server level roles.

Trace Flag 3625:
It limits the information for those users who are not part of the sysadmin role and it prevents sensitive information.

Trace Flag 3608:
It stops the SQL Server to start automatically backup and restore for all Databases except the Master database.

Trace Flag 3226:
When we are taking log backups frequently, we can avoid some unnecessary additional log information.

Trace Flag 3014:
Trace more information of error log during the backup operation.

Trace Flag 3505:
It disables all information about the instant file initialization.

In this post, I am sharing a TSQL script to find the status of SQL Server Trace.

The SQL Server Trace is very important for tracing the different SQL Server events like errors, object changes information and others.

Using this script you can find different information of the Trace like Trace is running or not, Type of the trace, File path of the trace.

You can also visit this article to enable and disable SQL Server Default Trace.

I am fetching require trace column using an sys.traces.

Below is a script:

SELECT 
	CASE T.is_default
		WHEN 1 THEN 'Default/System Trace'
		WHEN 0 THEN 'User Defined Trace'
	END AS TraceType
	,CASE T.status
		WHEN 1 THEN 'Running'
		WHEN 0 THEN 'Stopped'
	END AS TraceStrace
	,ES.session_id AS SessionID
	,ES.login_name AS LoginName
	,T.Path AS TraceFilePath
FROM sys.traces AS T
LEFT JOIN sys.dm_exec_sessions AS ES
	ON T.reader_spid = ES.session_id