Re: Agent Deadlock Errors

If you use Enterprise Manager, make sure that you are NOT polling for
status. Painting that little red X in EM causes a LOT of blocking which
contributes to your deadlock problems. If you are using queued updating as
a failover, I wouldn't run it on a continuous basis. That's because all of
your transactions are going through immediate updating. If you move your
queued agent to run on a staggered schedule to the distribution clean up,
most of your deadlocks are going to disappear.

--
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com


"David Grau" <DavidGrau@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DD11621D-2E56-42C6-B1B2-7AC8B8234F5F@xxxxxxxxxxxxxxxx
>I have been getting numerous deadlock errors in my Queued Reader agent and
> Distribution clean up agent.
> We are running transactional replication with immediate updating
> subscribers-with queued updating as failover. We have one primary server
> with 9 subscribers.
> My Queue Agent is set to run continuously.
> My Distribution clean up agent is set to run every 5 minutes.
> I have also implemented a scheduled job that runs every two hours to
> update
> the statistics in the distribution database.
>
> Is there any way to eliminate these deadlocks?
>
> Thanks,
> David Grau
> --
> Surprise & Delight


.

Relevant Pages

  • RE: Merge Agent is reporting deadlocks
    ... Agent locks records on the Publisher while it is synchronizing changes to ... Deadlock with the Update from the application. ... >>>Disconnecting from Publisher 'SQLBDG01PA' ...
    (microsoft.public.sqlserver.replication)
  • Re: replication deadlocked
    ... its likely the clean up agent deadlocking with the log reader ... Stop the clean up agent to see if it clears the problem. ... Also on sql 2005 you can use the deadlock trace or this (The text, ...
    (microsoft.public.sqlserver.replication)
  • RE: Distibution db cleanup will not run
    ... The 'sa' could be the owner of the agent ... right-click the job 'distribution clean up: ... 'xp_cmdshell' to READ and WRITE the directory instead of the job owner. ...
    (microsoft.public.sqlserver.replication)
  • Re: agents blocking each other
    ... would it be okay to schedule a job to run it? ... > Through Query Analyzer run the distribution clean up agent at a time when ... and the distribution clean up agent. ...
    (microsoft.public.sqlserver.replication)
  • RE: Deadlock on merge agent
    ... SQL Server 2000 build 818 and later changed how the Merge Agent ... This new design change might cause the Merge Agent to Deadlock ... agent to lock a smaller number of records and hopefully avoid the ...
    (microsoft.public.sqlserver.replication)