Hi all
I have a sql job that runs on about 10 servers in my company. It should normally take about 45 seconds to complete but on only one of these servers, it is taking up to 8 hours to run! I've checked everything I can think of as to what might be causing this but still haven't solved it. Now what i'd like to be able to do is schedule a trace to run on the server during the night when the job runs.
I;ve read up a bit on server side tracing (as i believe you cannot schedule profiler itself) but it sounds kinda complicated so i wondered if anyone can point me to some good sources of information regarding how to set this up, or whether anyone has done this before and can advise..
Thanks!
Div
I have a sql job that runs on about 10 servers in my company. It should normally take about 45 seconds to complete but on only one of these servers, it is taking up to 8 hours to run! I've checked everything I can think of as to what might be causing this but still haven't solved it. Now what i'd like to be able to do is schedule a trace to run on the server during the night when the job runs.
I;ve read up a bit on server side tracing (as i believe you cannot schedule profiler itself) but it sounds kinda complicated so i wondered if anyone can point me to some good sources of information regarding how to set this up, or whether anyone has done this before and can advise..
Thanks!
Div