Using the Default Trace in SQL Server
I have heard of the default trace in SQL Server. I know it’s on by default, but I don’t know how to use it. What can I do with the default trace?
2025-04-18
I have heard of the default trace in SQL Server. I know it’s on by default, but I don’t know how to use it. What can I do with the default trace?
2025-04-18
We all know that you should try to size tempdb appropriately, so it doesn’t need to autogrow shortly after starting up SQL Server. It isn’t always easy to do this. Therefore, when you first implement a new server and/or add new databases you should monitor the autogrowth events on tempdb. By monitoring the autogrowth events you can easily determine if you have sized tempdb appropriately.
2018-07-17
2,946 reads
If you are running an instance of SQL Server 2005 and above then most likely that instance is running the default trace. This default trace is a canned Profiler server side trace that automatically starts up when SQL Server starts. In this article Greg Larsen explains more about the default trace and shows you how to glean some event information from the trace files created by this background trace process.
2012-04-05
3,916 reads
By Chris Yates
Trust is the currency of the data economy. Without it, even the most advanced...
By Steve Jones
Another test with Copilot in SSMS (v22 P3) that didn’t go so well. This...
By Kevin3NF
If your production SQL Servers are still running 2016 (or older) you’re basically banking...
Comments posted to this topic are about the item Create an HTML Report on...
Comments posted to this topic are about the item SQL Server Ghosts
Comments posted to this topic are about the item The Selfish Case for Learning...