The performance monitor on our Win 2003 server often shows CPU at 25%, due
entirely to Sql Server Agent at a time when the agent shows no jobs running.
We stop and restart the agent, and CPU consumption drops to zero. A day or
two later and we're back to 25% again because of the agent. We're running
Sql Server 2000.
What is the problem?
Thanks,
Randy NeallDid you also watch with Profiler to see what's going on?
If you aren't using alerts, you could try deleting the demo
alerts that are installed by default. You can script out the
alerts first and then drop them.
-Sue
On Tue, 14 Mar 2006 21:33:25 -0500, "Randolph Neall"
<randolphneall@.veracitycomputing.com> wrote:
>The performance monitor on our Win 2003 server often shows CPU at 25%, due
>entirely to Sql Server Agent at a time when the agent shows no jobs running
.
>We stop and restart the agent, and CPU consumption drops to zero. A day or
>two later and we're back to 25% again because of the agent. We're running
>Sql Server 2000.
>What is the problem?
>Thanks,
>Randy Neall
>|||Thank you, Sue. We'll try to follow your advice.
Randy
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8f9f12dc24sqedodsd954e24flcs22tfat@.
4ax.com...
> Did you also watch with Profiler to see what's going on?
> If you aren't using alerts, you could try deleting the demo
> alerts that are installed by default. You can script out the
> alerts first and then drop them.
> -Sue
> On Tue, 14 Mar 2006 21:33:25 -0500, "Randolph Neall"
> <randolphneall@.veracitycomputing.com> wrote:
>
due[vbcol=seagreen]
running.[vbcol=seagreen]
or[vbcol=seagreen]
>
No comments:
Post a Comment