READ Data from default Trace

READ Data from default Trace to know when the objects are altered. If no database name is provided, it will run through all the databases.

Automating SQL Traces

Capturing the activity on a server when a problem occurs can be a challenge for many DBAs. This article shows how you can automate the capture of information when a CPU spike occurs.

The default trace in SQL Server - the power of performance and security auditing

Since the introduction of SQL Server 2005, there is a simple lightweight trace that is left running by default on every SQL Server. This provides some very valuable information for the DBA about the running server, but it isn't well-documented. Feodor Georgiev reveals many of the secrets of this facility and shows how to get reports from it.

Stairway to Server-side Tracing

Learn how to use the SQL Trace subsystem in SQL Server to audit your instances. This series will examine the basics of SQL Trace and teach you how to set up, schedule, and manage traces and the data generated.

Auto Generate an Hourly SQL Server Profiler Trace File

I would like the option on some servers of having a profiler trace running 24x7 in the background. I could then access and read these trace files to investigate issues after the fact - much like the default trace that came out with SQL 2005.

Default Trace Load of All 5 Files

The default trace keeps the last 20 meg of info, and a max of 5 files...This loads all 5 files into a table so it can be reviewed.

SQL Trace

Performance trace