December 28, 2017 at 11:37 pm
TEMPDB data gets full and when i check there are no long running transactions always
Hence , I captured wait info details on TEMPDB database using extended investigation for further investigation , details below
i found that wait type was network io during the time of tempdb full happened .There is a monitoring sql job which usually always run for all our prod servers and also this intsance . when i killed the job tempdb usage dropped although i doubt that this job is the culrprit but will still show as tempdb open transaction as it runs all the time . How to proceed ?
December 29, 2017 at 2:15 am
How often does this happen? The best place to start, I think, would be to download sp_whoisactive (if you don't already have it) and run it next time tempdb is full. That'll show the active processes that are using the most tempdb. What is it that's filling - the data file or the log file?
John
December 29, 2017 at 4:46 am
For more detail, you can go throught following link:
https://technet.microsoft.com/en-us/library/ms176029(v=sql.105).aspx
Regards
VG
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply