October 17, 2011 at 9:13 am
Every monday morning I arrive into the office to find that the tempdb has consumed almost all of the resources on the 200 GB partition where it resides. I am certain that the tempdb is growing so large as the result of an SSIS package that is scheduled to run on Sunday night....although I don't know how to track down the name of the package.
How can I figure out what the name of the package is that is causing these issues?
Also, my understanding is that the only way to shrink the size of the tempb is to restart the sql server service....I've been doing this but would like to know if there is a better way.
Thanks for you guidance.....
October 17, 2011 at 10:32 am
Can you look at the jobs scheduled and find the list of the scheduled jobs which run at that time, then look at them one at a time?
If not, another option would be to run the Profiler Sunday night and check it when you get in Monday morning. You should be able to find the query which is taxing your system through that approach.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply