Temp DB overflow
I and several others have had an issue with the temp DB growing out of control and not auto shrinking as it should.
After having a discussion on the emial group the other week we cam up with a possible solution thanks to Jim Bezdan.
Here is the solution:
**************************************************
A coworker was troubleshooting an issue on a few file servers where the c:\windows\system32\wbem\logs\FrameWork.log file was growing and filling up the C: volume (See http://support.microsoft.com/kb/836605 ) The problem as the article shows is that the Network Service account didn't have delete rights to the wbem\logs folder. The guy then went on all of the other servers, including my SMS primaries and found that two of them didn't have this permission set (the two that I was having problems with the tempdb log growth) He added the delete rights to the Network Service account for wbem\logs, restarted the servers and the tempdb log file growth problem went away. Although we never saw the FrameWork.log grow too big on the SMS servers, it was larger than it should have been before he made the change.
*************************************************
I tried this on the 2 server that where having an issue here and it has been running for about 2 weeks without any growth issue.
Hope this helps someone else out
Chris Stauffer <><