Default Trace

External 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.

2018-07-17

2,946 reads

External 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.

2012-04-05

3,916 reads

Blogs

Measuring What Matters: Operationalizing Data Trust for CDOs

By

Trust is the currency of the data economy. Without it, even the most advanced...

A Small LLM Fail

By

Another test with Copilot in SSMS (v22 P3) that didn’t go so well. This...

SQL Server Versions: Out With the Old, In With the Supported

By

If your production SQL Servers are still running 2016 (or older) you’re basically banking...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

SQL Server Ghosts

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Ghosts

The Selfish Case for Learning AI

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Selfish Case for Learning...

Visit the forum

Question of the Day

SQL Server Ghosts

For Halloween, what are ghost records?

See possible answers