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 Steve Jones
The greatest rewards come from working on something that nobody has words for. If...
By HeyMo0sh
Working in DevOps, I’ve seen FinOps do amazing things for cloud cost control, but...
Every organization I talk to has the same problem dressed up in different clothes....
Comments posted to this topic are about the item The day-to-day pressures of a...
Analysis Services (either the integrated workspace in Power BI or on a SQL Server)...
When thinking about the identity property and sequence objects, which of these can be used with numeric and decimal data types?
See possible answers