Default Trace

Technical Article

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.

You rated this post out of 5. Change rating

2018-07-17

2,946 reads

Technical Article

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.

You rated this post out of 5. Change rating

2012-04-05

3,916 reads

Blogs

Demo for Parameter Sniffing and Memory Grant Feedback

By

Disclaimer: The following is built with Claude Code. Just need to justify my $100/mo...

My Social Media Rules

By

I developed these rules a while back, before COVID. I had a period of...

Why Use TRY_PARSE(): #SQLNewBlogger

By

Someone asked why I would use TRY_PARSE after I posted a question at SQL...

Read the latest Blogs

Forums

Partitioning a table with TEXTIMAGE_ON option

By Brandie Tarvin

I have a table that ends in ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]. I'm about to...

OUTER APPLY Fundamentals: Part 2

By Imran2629

Comments posted to this topic are about the item OUTER APPLY Fundamentals: Part 2

Building Great Software

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Building Great Software

Visit the forum

Question of the Day

The Range of Customers

I have this data in the OrderHeader table in a SQL Server 2025 database (ordered by CustomerID ASC):

orderid orderdate               customerid complete
3       2025-05-10 00:00:00.0002          1
21      2024-01-10 00:00:00.0003          1
15      2023-10-28 00:00:00.0004   1
13      2025-03-08 00:00:00.0006          1
11      2024-04-02 00:00:00.0007          1
If I run this query, how many rows are returned?
SELECT *
 from dbo.OrderHeader
 where customerid between 3 and '6'

See possible answers