3 ms·
Funnily enough I encountered something similar years ago on Microsoft SQL Server 2005. Never got to the bottom of it either.
by philjohn 10y ago
Funnily enough I encountered something similar years ago on Microsoft SQL Server 2005.
Never got to the bottom of it either.
- dspillett 10y agoA lot of cases I've seen where tempdb suddenly grows massively is an runaway Cartesian product in a query. Sometimes this is intentional but was never expected to be used on large data, but usually it is accidental and worse an inexperienced DB person has "fixed" the problem with multiplied output rows by adding "distinct" instead of fixing the query logic properly.