Feeds:
Posts
Comments

Archive for the ‘Trace Flag’ Category

Returns the resources and types of locks that are participating in a deadlock and also the current command affected, in an XML format that does not comply with any XSD schema.

Scope: global only

 

Advertisements

Read Full Post »

Returns the resources and types of locks participating in a deadlock and also the current command affected.

Scope: global only

 

Read Full Post »

Limits the amount of information returned in error messages. For more information, see Metadata Visibility Configuration.

Scope: global only

 

Read Full Post »

Database Trace :- 3226

1. Successful backup entries are not added to the SQL Server error logs.
2. Entries are prohibited from being logged in the System event log.
3. Only failed backup event entries are logged.
4. No successful backup entries are logged.

A trace flag (3226) can be either specific to a session or a global trace flag.

A trace flag can be switched on or off by using the dbcc traceon and dbcc traceoff command

DBCC TRACEON(3226)
DBCC TRACEOFF(3226)

Note:- You should ensure that no script is dependent on any successful backup entries that are logged either in the error log or in the System event log.

Read Full Post »