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 ReviewMyDB
Index maintenance has always meant nightly jobs and a window you have to defend....
By Steve Jones
One of the things I’ve been requesting for a number of years is cost...
By Steve Jones
“Don’t aim to have others like you; aim to have them respect you.” –...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item SQL Server Still Wins
Comments posted to this topic are about the item DBCC CHECKDB Limits I
When running DBCC CHECKDB on SQL Server 2025, can I include the Resource Database?
See possible answers