Re: Merge replication stopping

Tech-Archive recommends: Speed Up your PC by fixing your registry

We have the job running every minute and it seems to work fine. I have
noticed that the retry doesn't work like one would think it should.

If you go to Merge Agent History, Session Details, Error Details, you should
get more information on why it can't continue. We get a lot of deadlocks
causing the agent to fail, but when it picks back up a minute later it
usually works fine.

Dylan Peters

"Hilary Cotter" wrote:

> Yes, it is typically a transitory error. Many dba's run their merge agents
> in infinite loops by having step 3 looping back to step 1.
>
> --
> 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
>
> "Salvador" <Salvador@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:723F7F3D-6BE0-4205-B79F-01CA227E7EF7@xxxxxxxxxxxxxxxx
> > Hi All,
> >
> > I have selected merge replication because both servers are constantly
> > updating information. We have continuous merge replication (push) and
> > everything works pretty good.
> >
> > The problem is in some occassions the job stops saying that it can not
> > enumerate the changes on the subscriber, if I restart it works fine. This
> is
> > causing more than a headache because we always have to be watching if
> > replication is working. I try to change the job to restart when it fails
> but
> > it doesn't work.
> >
> > I have one publisher with the distributor on the same machine pushing the
> > continuous merge to one subscriber.
> >
> > Can this happen because the subscriber is busy and the job can connect?
> Have
> > anyone seen this happening?
> >
> > Thanks a lot
>
>
>
.

Relevant Pages

  • Re: undocumented agent profile parameters
    ... dedicated when you the merge replication related procs and commands are run ... I would venture to say that the performance of the merge agent is more ... When I hear the words performance and blocking on the publisher with ... Is "source" a publisher or subscriber? ...
    (microsoft.public.sqlserver.replication)
  • Re: Add Merge Subscr w/ nosync doing may metadata updates???
    ... Your publication is different in production. ... Looking for a SQL Server replication book? ... 1Mill+ rows), performed table maintenance at subscriber, then added ... Merge agent so far has performed 14000 Updloaded actions (each individaul ...
    (microsoft.public.sqlserver.replication)
  • Re: The process could not query row metadata at the Subscriber
    ... Source: Merge Replication Provider ... The process could not query row metadata at the 'Subscriber'. ... All my servers are SP3a, and I've already tried to pass to the agents ... >> change the agent profile settings, ...
    (microsoft.public.sqlserver.replication)
  • Merge Replication Failures
    ... I have replication setup between server A & B, ... is distributor/publisher & B is subscriber. ... only one merge publication and one subscription each. ... schedule for the snapshot agent to kick in. ...
    (microsoft.public.sqlserver.replication)
  • Re: Transactional Replication Issues
    ... The process could not connect to Subscriber 'SQLServer2'. ... 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 ...
    (microsoft.public.sqlserver.replication)