Is the Hash Match between table6 and table1 causing TEMPDB to blow up? sqlenforcer 2014-08-28 18:20:52 Large query causing 140GB TEMPDB to run out of space. It appears that the hash match may be a problem. Without seeing the query, is there any advice? Aaron Bertrand 2014-08-28 18:26:54 Why is the sort after the hash match necessary? Can you create an index that supports it to remove the sort operator at all? How about the missing index SQL Server suggested for table1? Why is table 5 a heap? Can you add a clustered index, or expand the existing non-clustered index so a RID lookup is not required? Can't really get more specific than that without seeing the query (some of these things may just disappear with a rewrite). sqlenforcer 2014-08-28 21:22:04 Thank you Aaron, I'll look at your advice and return if needed. SQLkiwi 2014-08-28 22:38:15 A post-execution plan would be more helpful than the current estimated one. August 28, 2014 No Comments Post navigation Same Query, Two Plans, One StinksNeed to improve the running time of the SP. Need help.