Default Trace

Using SQL Server's Default Trace to Identify Autogrow Events in tempdb

  • Article

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.


2,946 reads

A Few Cool Things You Can Identify Using the Default Trace

  • Article

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.


3,916 reads


Weekly reading #19


Good afternoon folks! It is Monday Tuesday already after a long weekend in Poland....

The Constant and Constantly Changing Role of the DBA


I’ve been working in and around data for over 30 years now. My title...

Power BI Monthly Digest – June 2019


In this month’s Power BI Digest with Manuel Quintana [Blog | Twitter] and I...

Read the latest Blogs


unable to install SQL Server 2014

By Srinivas Sista

Hi, I am trying the install SQL Server 2014 enterprise edition on Windows 2016...

What's the CMK?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What's the CMK?

Spread the Word about Basic Security

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spread the Word about Basic...

Visit the forum


SQL Server Q&A from the SQLServerCentral community

Get answers