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
Default Trace
Using SQL Server's Default Trace to Identify Autogrow Events in tempdb
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
A Few Cool Things You Can Identify Using the Default Trace
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
Blogs
Keeping Redshift System Table History Past 7 Days with S3 Tables
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
Updating the Data API Builder
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget
I am excited to host T-SQL Tuesday for the first time. I want to...
Forums
Practical Ways to Approach SQL Server Problems and Case Studies
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Measuring Productivity
Comments posted to this topic are about the item Measuring Productivity
Importing Excel files into SQL Server using DuckDB and Python
Comments posted to this topic are about the item Importing Excel files into SQL...
Question of the Day
Tracking All the Queries
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers