Hi All,
Sometimes, I run into a situation where tempdb file gets full and by the time I look into it, the session that might have caused the tempdb to grow significantly might have been already gone. At that point, I can't use sys.dm_db_session_space_usage or sys.dm_db_task_space_usage to find out about the session/query because the session doesn't exist anymore. So, assuming that the query is still in the cache but the session is already gone, is there a DMV that can give me information about how much tempdb space this particular query consumed?
I am using SQL 2008r2 and SQL 2014.
I appreciate the answer.
thanks,
Raj