December 2, 2005 at 12:40 pm
I have a problem with pausing the Profiler on one of my SQL servers.
When the trace is running and I click Pause, then it takes about 1 hour for the trace to stop. Sometime, when testing this is very slow.
How can I fix it?
Thanks a lot,mj
December 2, 2005 at 12:44 pm
Is your SQL Server extremely busy during this same hour? This seems to me to be more of a resource problem than a Profiler problem. I would say that the Profiler is either waiting for CPU time or waiting for something within SQL Server before it can stop.
December 2, 2005 at 12:54 pm
extreamly busy, and probably there's no resoures left for the profiler at all.
But is there a way to stop it anyway without to kill the profiler process. Sometimes I have other traces that I need to look at and keep...
Thanks a lot,mj
December 2, 2005 at 1:00 pm
I don't know of a way, outside of killing the process, that would pause your profile if it is waiting for resources. You've clicked the pause button and the pause request is queued up and waiting for CPU or SQL Server to process the pause and pause Profiler for you.
It sounds like your test system is too small for your application. Being able to run performance and diagnostic tools is an important part of testing applications. If your test system is resource bound to the point where you cannot run performance and diagnostic tools, you may want to petition for new test hardware.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply