External Article

Using SQL Server's Default Trace to Identify Autogrow Events in tempdb

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.

Blogs

Voice of the DBA | Writings from Steve Jones, the Voice of the DBA

By

Houston AI-Lytics 2026–Powerpoint Slides Thanks to everyone for attending my session on running a...

The Book of Redgate: Do the Right Things

By

I do believe that Redgate has been very customer focused since it’s inception. I’ve...

How to Connect to SQL Server When Nothing Else Works – DAC

By

It's 2 AM. Your phone is going off. Users can't connect to the application,...

Read the latest Blogs

Forums

Warning: Could not open global shared memory to communicate with performance DLL

By water490

Hi everyone I am getting below warning when I run SSIS: Warning: 0x80049304 at...

Let's Talk Community Events!

By Pat Wright

Comments posted to this topic are about the item Let's Talk Community Events!

that one limitation in replication

By stan

Hi as shown below a replication target requires a primary key.  if we want...

Visit the forum

Question of the Day

Detecting Deadlocks

By default, how often is the SQL Server Database Engine checking for deadlocks?

See possible answers