Idle Sql Agent consumes CPU

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:
> >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
> >
> >
>

Idle Sql Agent consumes CPU

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
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:

>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... [vbcol=seagreen]
> 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
>
sql

Idle Sql Agent consumes CPU

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]
>

Identity range managed by replication is full and must be updated by a replication agent.

Hello,

I'm getting the following error message when I try add a row using a
Stored Procedure.

"The identity range managed by replication is full and must be updated
by a replication agent".

I read up on the subject and have tried the following solutions
according to MSDN without any luck.(http://support.Microsoft.com/kb/
304706 )

sp_adjustpublisheridentityrange (http://msdn2.microsoft.com/en-us/
library/aa239401(SQL.80).aspx ) has no effect

For Testing:

I've reloaded everything from scratch, created the pulications from by
running the sql scripts generated,created replication snapshots and
started the agents.

I've checked the current Identity values in the Agent Table:

DBCC CHECKIDENT ('Agent', NORESEED)
Checking identity information: current identity value '18606', current
column value '18606'.

I check the Table to make sure there will be no conflicts with the
primary key:

SELECT AgentID FROM Agent ORDER BY AgentID DESC
18603 is the largest AgentID in the table.

Using the Table Article Properties in the Publications Properties
Dialog, I can see values of:

Range Size at Publisher: 100,000
Range Size at Subscribers: 100
New range @. percentage: 80

In my mind this means that the Publisher will assign a new range when
the Current Indentity value goes over 80,000?

The Identity range for this table cannot be exhausted! I'm not sure
what to try next.

Please! any insight will be of great help!
Regards,
Bm(miller.brettm@.gmail.com) writes:

Quote:

Originally Posted by

I'm getting the following error message when I try add a row using a
Stored Procedure.
>
"The identity range managed by replication is full and must be updated
by a replication agent".
>
I read up on the subject and have tried the following solutions
according to MSDN without any luck.(http://support.Microsoft.com/kb/
304706 )
>
sp_adjustpublisheridentityrange (http://msdn2.microsoft.com/en-us/
library/aa239401(SQL.80).aspx ) has no effect

You have better luck in microsoft.public.sqlsever.replication. Myself,
I have very little experience of replication.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx