Re: agents blocking each other

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

From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 03/01/05


Date: Tue, 1 Mar 2005 06:57:22 -0500

btw - with pull subscriptions you have no central point of administration.

For instance, with push you connect to your publisher in EM and manage your
replication solution. With pull you have to connect to each subscriber and
expand replication monitor to see errors. Make sure you use Replication
Monitor Group to show all your subscribers (use Tools, Replication, Show
Replication Monitor Group and go to the bottom node and right click on
Replication Monitor Group and select add distributor to monitor).

-- 
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
"Kristy" <pleasepostreply@here.com> wrote in message
news:enALdThHFHA.1176@TK2MSFTNGP12.phx.gbl...
> Thanks.
>
> Why is it happening and what do the suggestions you provide buy me? Also,
> would it be okay to schedule a job to run it? That way the off peak hours
> could be utilized best. (I do have to sleep at some point ;-)  )
>
> Thanks again,
> (and still anxiously awaiting my order to arrive)
> Kristy
>
>
> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
> news:u0iLc2gHFHA.2132@TK2MSFTNGP14.phx.gbl...
> > Avoid using EM.
> >
> > Through Query Analyzer run the distribution clean up agent at a time
when
> > there are few users on the system.
> >
> > Consider moving to pull subscriptions and possibly a remote distributor.
> >
> > -- 
> > 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
> >
> > "Kristy" <pleasereplyby@posting.com> wrote in message
> > news:%235Ev4idHFHA.3628@TK2MSFTNGP15.phx.gbl...
> > > Contantly there seems to be a blocking issue between the distribution
> > agent,
> > > the log agent, and the distribution clean up agent.
> > > This will eventually cause one of the agents to shut down (the log
> agent).
> > > What can I do to elevate this situation and why is it happening?
> > >
> > > --Kristy
> > >
> > >
> >
> >
>
>


Relevant Pages

  • Re: Deadlock between Distribution Agent and Distribution Agent Cle
    ... Another option will be to put your distribution database in bulk copy ... Looking for a SQL Server replication book? ... The Distribution Agent Cleanup job code ... and only reading the transactions committed some ...
    (microsoft.public.sqlserver.replication)
  • Re: Error at parameter 93 during datastream processing of paramete
    ... the distribution agent fails with the message. ... Message: Replication-Replication Distribution Subsystem: agent ... Source: ODBC SQL Server Driver ... > pack/hotfix level on each of the servers involved in this replication setup? ...
    (microsoft.public.sqlserver.replication)
  • Re: Agent Deadlock Errors
    ... I am not sure about updating the statistics in the distribution database. ... clean up agent is locking with. ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Agent Deadlock Errors
    ... Changed the History Cleanup Agent to run every 10 minutes, ... Changed the Distribution Cleanup Agent to run every 5 minutes, ... Turned off the auto-refresh of the Replication Monitor on my Enterprise ... >>> Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Transactional Replication Issues
    ... distribution agents will allow the snapshot agent to run (fewer processes ... Server Agent configured to run many jobs? ... configured all you replication agents to run under explicit Windows account. ...
    (microsoft.public.sqlserver.replication)