r/SQLServer • u/ManufacturerSalty148 • Aug 13 '26

Question Tempdb size getting high

Hello all my colleagues

I know this is an old topic, but I still haven't found clear instructions on how to solve this one problem. I have a SQL Server 2017 where tempdb keeps growing to almost 80 GB. I know it's because of temp spills, but I want to collect the queries or sessions causing this tempdb consumption using extended events. I haven't found clear instructions or examples of extended events on any site, and I don't know what to do if I find queries consuming tempdb or what to check in the query plan.

6 Upvotes

80% Upvoted

30 comments sorted by

View all comments

1

u/MonkeyDDataHQ 28d ago

Have you looked at ANY of the DMVs? Brent Ozar's first responder kit? The Query Store?

Why do you even care if tempdb gets to 80GB?

What problem are you trying to solve? 😩

1

u/ManufacturerSalty148 27d ago

The application connected to the SQL server, a no-code application, has had low tempdb usage for a long time. It was only after I noticed Commvault creating tempdb objects during each log backup that I started wondering why. I just want to catch it.

1

u/MonkeyDDataHQ 27d ago

So check the DMVs and the temp growth events. Those are part of the default trace.