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

Query multiple Azure SQL Databases

By

I was sick of changing context in Azure Data Studio while cleaning up things...

KDA: Echoes of Deception - Case 3

By

The crime spree in Digitown is not ending. This time 20 cars have been...

The Book of Redgate: Do Your Best Work

By

One of our mission statements in the Book of Redgate says: attempt to do...

Read the latest Blogs

Forums

CAST(VARCHAR(n)) resolved performance issue?

By mikael_ljunghorn

Hi, I would love to hear if anyone can tell me why a CAST...

isnull, coalesce overhead

By stan

hi, one of our sister division's erp extract view is going thru at least...

is there an elegant way for agent notification to show failure if any step fails

By stan

hi our corp dw load sqlagent job goes to the next step on the...

Visit the forum

Question of the Day

The Internals of Writing a Page

In SQL Server, when the buffer manager write pages to disk, page protection is added to the pages. There are two types of protection: torn page protection and checksum page protection. What happens with regards to concurrency with page protection during writes?

See possible answers