Hello,
I have a merge replication scenario where occasionally the
subscription server will go offline for a period of time.
It seems that when this is the case the merge agent stops
and when the subscription server becomes available I have
to manually restart the merge agent for syncronization to
continue. Does this seem right or should the merge agent
continue to run even while the subscription server is
unavailable so that when the subscription server becomes
available syncronization will continue automatically?
Any help would be appreciated!
Thanks in advance.
this behavior is by design. To fix it you should schedule the merge agent to
run every 10 minutes. This way it will continually retry until it succeeds.
You might also want to recreate the subscription as a pull subscription.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Jerry G." <anonymous@.discussions.microsoft.com> wrote in message
news:1c4e701c45257$6cd0c470$a101280a@.phx.gbl...
> Hello,
> I have a merge replication scenario where occasionally the
> subscription server will go offline for a period of time.
> It seems that when this is the case the merge agent stops
> and when the subscription server becomes available I have
> to manually restart the merge agent for syncronization to
> continue. Does this seem right or should the merge agent
> continue to run even while the subscription server is
> unavailable so that when the subscription server becomes
> available syncronization will continue automatically?
> Any help would be appreciated!
> Thanks in advance.
Friday, March 23, 2012
Merge Agent
Labels:
agent,
database,
merge,
microsoft,
mysql,
occasionally,
offline,
oracle,
period,
replication,
scenario,
server,
sql,
thesubscription,
time
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment