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 |
|
juicyapple
Posting Yak Master
176 Posts |
 Posted - 2008-10-08 : 21:44:09
|
| I encountered tempdb full error, and found out that there is one open transaction which caused the tempdb and disk space full. Not sure what is it, any help?dbcc opentranOldest active transaction:SPID (Server process ID) : 56UID (User ID) : -1Name : sort_initLSN : (8543:18976:237)Start time : Oct 7 2008 11:55:45:367DBCC execution completed. If DBCC printed error message.... |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-10-08 : 23:14:38
|
| Then why don't you kill the SPID?Use DBCC inputbuffer(Spid) to find out. Restarting SQL Services creates fresh TempDB. |
 |
|
|
juicyapple
Posting Yak Master
176 Posts |
Posted - 2008-10-09 : 02:39:30
|
yes, our DB admin has solved it. But we need to find out why there is one process hangs there, causing the log file full. I just know that it is caused by sort_init in tempdb, which is opened when use order by command. Anyway to trace out what jobs or store procedure related?quote:
Originally posted by sodeep
Then why don't you kill the SPID?Use DBCC inputbuffer(Spid) to find out. Restarting SQL Services creates fresh TempDB.
|
|
|
|
|
|
|
Sort_Init