Why TempDB Is Slowing Down Your Entire Server (And You Don’t Notice!) 🔥

👉 Why TempDB Is Slowing Down Your Entire Server (And You Don’t Notice) 🔥

Hi SQL Server Guys,

👉 If you missed my previous post, check it out here:
Nested Loop vs Hash Join vs Merge Join – The Truth Nobody Explains

The usual intro...

Your server is slow.
CPU looks fine.
IO looks fine.
Execution plan looks… acceptable.

👉 So what’s killing performance?

TempDB.

And the worst part?

👉 You often don’t even see it.

🧠 What is TempDB really?

TempDB is a shared system database used by SQL Server for temporary operations.

It is involved in a lot of aspects:

  • Temporary tables (#temp)
  • Table variables
  • Sorting (ORDER BY)
  • Hash operations (JOIN / AGG)
  • Spills to disk
  • Version Store (snapshot isolation)

💣 TempDB is not optional: It is involved in almost every complex query.

⚙️ When SQL Server Uses TempDB

SQL Server uses TempDB whenever memory is not enough or when intermediate results are required.

  • Large SORT operations
  • Hash joins / aggregations
  • Row versioning
  • Spool operators

👉 If memory is insufficient then SQL Server spills to TempDB (no good!)

🔥 The Silent Killer: Spills

A spill happens when SQL Server runs out of memory and writes data to TempDB.

Types of spills:

  • Sort Spill
  • Hash Spill

💣 Disk is thousands of times slower than memory.

👉 A query that should run in milliseconds can suddenly take seconds.

🔥 Temp Tables & Table Variables

Temp tables are heavily used in real-world workloads: 


CREATE TABLE #TempOrders
(
    id INT,
    amount MONEY
);

INSERT INTO #TempOrders
SELECT id, amount
FROM Orders;

👉 Every insert = writes into TempDB 👉 Every index = more writes

💣 Temp tables are not “free memory”… they are real IO operations.

🔥 Version Store (Hidden Beast)

When using:

  • READ COMMITTED SNAPSHOT
  • SNAPSHOT ISOLATION

SQL Server stores row versions in TempDB.

💣 Long transactions = massive TempDB growth

👉 This is one of the most common production issues.

⚠️ Common Mistakes

  • Too few TempDB files (one mdf file per CPU? ...we will see in next posts)
  • Slow disk (no SSD)
  • No monitoring of spills
  • Overuse of temp tables
  • Ignoring version store growth

💣 TempDB contention can slow down the entire instance. Keep in mind that all the databaes shares the SAME TempDB Databases! 

🚀 Summary of the Improvements Across SQL Server Versions

  • SQL Server 2016+ → automatic TempDB configuration improvements
  • SQL Server 2019 → memory-optimized TempDB metadata
  • SQL Server 2022+ → better spill handling and memory grants
  • SQL Server 2025 → improved parallelism + TempDB contention reduction

👉 But even with improvements bad queries still kill TempDB.

🧪 Benchmark – Spill Impact

Scenario Execution Time TempDB Writes
No Spill 123 ms Low
Sort Spill 840 ms High
Hash Spill 1270 ms Very High

💣 Same query. Same data. Just less memory → 10x slower.

🔍 How to Detect TempDB Problems 


SELECT 
    SUM(user_object_reserved_page_count) * 8 AS KB_User,
    SUM(internal_object_reserved_page_count) * 8 AS KB_Internal,
    SUM(version_store_reserved_page_count) * 8 AS KB_Version
FROM sys.dm_db_file_space_usage;

👉 Monitor:

  • Spills (execution plan warnings)
  • TempDB growth
  • Wait stats (PAGELATCH, WRITELOG)

💣 My Final Thought

“TempDB is not just a temp space…
it’s the hidden engine behind your performance.”

👉 If TempDB is slow… everything is slow.

📚 Related Posts

Comments

Post a Comment

I Post più popolari

Speaking to Sql Server, sniffing the TDS protocol

Image
Hello friends!  If yesterday you read my post and found it definitely boring (for the topic of course and not for how it was written to the author 😁) well today I promise you that the topic will be much more interesting! Let's talk about Sniffing , let's talk about going to see what happens when we "log in" or when we send a Query to SQL Server.  We will do this by taking a look to the little known tabular data stream (TDS) protocol built on top of the TCP/IP protocol. Ready! The TDS protocol What is the Tabular data stream (TDS) protocol?  The TDS is the protocol used by the SQL Server client Net-Library to communicates with SQL Server . TDS is specific to SQL Server and it is a low-level protocol that specifies both commands and data in a specific arrangement.  TDS encapsulate the TCP/IP protocol. Sniffing TDS packets you can read from the network the requests that your application do to the SQL Server and read the answer .   How to Sniff data from the ne...
Read more

SQL Server, find text in a Trigger, Stored Procedures, View and Function. Two ways and what ways is better

Image
Hi guys, Welcome back! Today a light post about a question that has been asked to me several times. The question is: how to  search for text inside a trigger or a stored procedure ? We have two different ways. A first way using a system view called syscomments: SELECT obj.xtype, text , * FROM sysobjects obj JOIN syscomments com on obj.id = com.id WHERE TEXT like '%text_that_i_am_searching_for%' A second way using a system view called sql_module: SELECT o. name AS Object_Name, o. type_desc , m. definition FROM sys.sql_modules m JOIN sys.objects o ON m. object_id = o. object_id WHERE m. definition Like '%text_that_i_am_searching_for%' ;   Another question is? What differences do we have in using one way instead of the other? Which solution is better? You have to consider that the system view sys.syscomment is obsolete and will be removed sooner or later. So don't use it in production enviroiments. The sys.sql_m...
Read more

SQL Server, Avoid that damn Table Spool!

Image
Hi guys, Welcome back for another post! A light one inspired from what i do during my work: many times I optimize queries rewriting them or adding index and i like it very much! Sometimes you need to use a little imagination, but everything you learn ... sooner or later it will come in handy! Enjoy the reading mates! Avoid the Table Spool, when you can A few days ago I came across a query whose execution time was very high ... or so it was for the client complaining about the problem. Before recreating it, let's create the structures and fill the tables with some data Create table PriceList (Id int identity (1,1) primary Key ,Code Varchar (20)) Insert into PriceList (code) select top 1000 right( '0000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Insert into PriceList (code) select top 4000 right( '1000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Create table OrdersList (Id int identity...
Read more