Re: Agent Deadlock Errors

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Phil Vaughn and experience.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

"Michael Hotek" <mike@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uWt1i2JFGHA.3984@xxxxxxxxxxxxxxxxxxxxxxx
> Just where in the hell are you getting THAT information? Where's your
> proof that it doesn't scale beyond 10 subscribers? That would mean one of
> my customers implementations is completely impossible, because they have
> 98 subscribers doing queued updating right now.
>
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
>
> "Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
> news:uxQSahuEGHA.2292@xxxxxxxxxxxxxxxxxxxxxxx
>> Queued replication is not really scalable beyond 10 subscribers, you may
>> be hitting its upper limit. I would suggest you run the queued agents on
>> a schedule, every 5 minutes or so and perhaps stagger their schedules.
>> Also Close down Enterprise Manager as much as possible as this causes
>> locking with the replication agents (actually its the refresh rate which
>> does this).
>>
>> --
>> Hilary Cotter
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.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: 2005 Replication Monitor != MSdistribution_status.undelivCmdsI
    ... IIRC virtual subscribers are anonymous subscribers. ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ... "Hilary Cotter" wrote: ...
    (microsoft.public.sqlserver.replication)
  • Re: Help with SSL Encryption
    ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ... If you deploy your subscribers via a pull and unc you need the ...
    (microsoft.public.sqlserver.replication)
  • Re: How to get notification about completion of applying snapshot
    ... try looking for> Applied script 'Table4_4.dri' if that is the last thing to ... Looking for a SQL Server replication book? ... Hilary Cotter wrote: ... pull-distribution agent. ...
    (microsoft.public.sqlserver.replication)
  • Re: Change QueryTimeout
    ... It could be transactions queued in the distribution database. ... Looking for a SQL Server replication book? ... "Hilary Cotter" wrote: ... I cannot get to agent properties because the subscribers are ...
    (microsoft.public.sqlserver.replication)
  • Re: Prcess could not execute sp_MSadd_repl_commands27hp
    ... I upped the QueryTimeout to 600 and I'm still getting the timeout... ... Looking for a SQL Server replication book? ... At the time the below error occured, the "Distribution clean up: ... The agent failed with a 'Retry' status. ...
    (microsoft.public.sqlserver.replication)