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


Interview with Greg Low


This is the sixth interview we have done. This time our guest is Greg...

Azure SQL Database Types


I want to do a quick summary post of the many different types of...

Azure SQL Database – Azure Portal Updates


A small but useful change has been made to the Azure Portal for Data...

Read the latest Blogs


Is Data the Future of the Vibrant Web?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Is Data the Future of...

Users cannot run/view a report, but can all the other reports. How?

By Rod at work

I've got a problem which I can't figure out. I've got 3 SSRS reports,...

Find the Originating DB Name, Not the Current DB Name

By fahey.jonathan

I am considering creating a "Tools" (or similar name) database to hold common procedures...

Visit the forum


SQL Server Q&A from the SQLServerCentral community

Get answers