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.

2018-07-17

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.

2012-04-05

3,916 reads

Blogs

Daily Coping 18 Sep 2020

By

I started to add a daily coping tip to the SQLServerCentral newsletter and to...

Optimize for Unknown for Inline Table-Valued Functions

By

I had a curious performance issue today. An inline table-valued function (iTVF) was performing...

Daily Coping 17 Sep 2020

By

I started to add a daily coping tip to the SQLServerCentral newsletter and to...

Read the latest Blogs

Forums

Number weeks from April to September for every year

By deepkaur@outlook.com

I want to number weeks from April to September for every year, such that...

Index Fragmentation

By stevec883

I am looking into fragmentation in one of my databases and ran across these...

SSIS package with Multiple Streams

By sizal0234

I have a package with has multiple streams and calls the same SP. Why...

Visit the forum

Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers