Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dbalearner
Constraint Violating Yak Guru
272 Posts |
 Posted - 2009-05-14 : 20:25:36
|
| I have yesterday the TEMPDB ran out and was full, subsequently I have moved out the current location for the TEMPDB and rebooted the system. Now it is all working fine.My question to all patrons, how to find out in the Server's Instance which database has caused TEMPDB to be full.I have searched in the past errorlog file but has no evidence. I have queried using the DMV's (sys.dm_db_file_space_usage, sys.dm_db_session_space_usage etc) but of no help.Can anyone let me tell as how I can find out the Database (transaction) caused the TEMPDB to full?Thanks all |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-05-14 : 23:26:02
|
| Check inside stored procedure or function if you are temp table or table variable which dumps lot of records and run frequently. You have to see in profiler for what's going on. |
 |
|
|
dbalearner
Constraint Violating Yak Guru
272 Posts |
Posted - 2009-06-09 : 17:36:00
|
| Thanks The query which ran for 3 hours has swallowed the TEMPDB Space.It got resolved. |
|
|
|
|
|
|
Database Queried