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

From DBA or Data Engineer to AI Engineer: A Realistic Path

By

If you spend your days tuning queries, managing pipelines, or keeping a production database...

Asynchronous Replication of Snapshots from an ActiveCluster Pod to a Third Array

By

I’ve been rebuilding my three-site SQL Server demo lab, and I ran into something...

SQL Server gMSA: Why So Many DBAs Still Aren't Using It in 2026

By

SQL Server gMSA: Why DBAs Still Aren't Using It in 2026 ...

Read the latest Blogs

Forums

Never is Not the Policy

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Never is Not the Policy

Automating SSAS Multidimensional Security Audits with PowerShell

By Pablo Echeverria

Comments posted to this topic are about the item Automating SSAS Multidimensional Security Audits...

Rebuilding All Indexes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Rebuilding All Indexes

Visit the forum

Question of the Day

Rebuilding All Indexes

I have added a few indexes to one of my tables in SQL Server 2025:

ALTER TABLE dbo.CustomerContact
ADD CONSTRAINT PK_CustomerContact
    PRIMARY KEY (CustomerID);

-- Create index on CustomerEmail
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (CustomerEmail);
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disable
I see this when I check the index status:Index status for CustomerContactI decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContact
After I do this, what will I see for the index status?

See possible answers