Optimizing tempdb configuration with SQL Server 2012 Extended Events

One of the most obvious bottlenecks in the performance of tempdb is caused by PAGELATCH, in-memory latch contention on the allocation bitmap of each data file used. We can use one of the rules-of-thumb to choose what should be roughly the best number of files, but how then do you check to see whether you've got it right for your data and workload?

How to Performance Tune the Microsoft SQL Server tempdb Database

If your SQL Server’s tempdb database is heavily used by your application(s), consider locating it on an array of its own (such as RAID 1 or RAID 10). This will allow disk I/O to be more evenly distributed, reducing disk I/O contention issues, and speeding up SQL Server’s overall performance.

Tempdb Space Usage in SQL Server

We all know how important tempdb is and know that tempdb gets recreated every time SQL Server is restarted. Here we dig a little deeper to focus on how space is used inside tempdb.

Identify Allocation Contention in TEMPDB

Identifies potential page allocation contention in TEMPDB.

TempDB usage per active session

Lists the TempDB usage per each active session.

TempDB

TempDB

SQL Server Tempdb Usage and Bottlenecks tracked with Extended Events

How do I effectively find out if the Tempdb database is suffering from an allocation bottleneck? Should I create multiple TempDB files per core on this server to improve performance? How do I check this information programmatically?

Re-size TempDB files

Managing TempDB can be a bit tricky at times. Most people know how to increase the size, but what about reducing it? New author Amar Pogaku brings us two techniques for shrinking tempdb.

TSQL - tempdb