February 22, 2006 04:22 PM

Searching for a Trace

Solving the mystery of SQL Server 2005's default trace enabled option
Rating: (0)
SQL Server Magazine
InstantDoc ID #48939
As I was researching new server-configuration options in SQL Server 2005, I came across an option called default trace enabled. I checked the SQL Server Books Online for the current build, and found the following information: Use the default trace enabled option to enable or disable the default trace log files. The default trace functionality provides a rich, persistent log of activity and changes primarily related to the configuration options.

The BOL ...

...This article is for paid Professional Members only.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Professional Membership

Monthly

Annual

VIP Membership

Monthly

Annual

Add a Comment

I was wondering about this trace for a while, thanks for this article.

Take Care!

Marcos7/16/2009 1:39:55 PM


Update:
There is a much better way to look at the trace properties than using
SELECT * FROM ::fn_trace_getinfo(default)

You can query the sys.traces metadata view to see not only all the information from the function,but lots more besides. And it's much easier to interpret.

See my blog post for more details:
http://sqlblog.com/blogs/kalen_delaney/archive/2006/10/08/Metadata-for-traces.aspx

~Kalen

KALEN5/22/2007 10:53:35 AM


I think the trace Kalen has described is related to the reports that Management Studio provides. As far as i know, there is some data on those reports that you could only get if you had some kind of trace running on background. Does any body agree?

Hugo3/14/2006 7:16:19 AM


You must log on before posting a comment.

Are you a new visitor? Register Here
GOOGLE LINKS
SPONSORED LINKS
FEATURED LINKS