Merge replication agent schedules question.

I am using SQL Server 2000 on Windows 2003 Server. I have two identical
machines running this configuration. Machine A is primary, machine B is
backup. I have setup a merge replication as such: Distributor running on B,
publisher on A, pull subscriber on B. These machines are installed at a
customer site on a new network that exeriences outages and errors. I
currently have the schedule for the snapshot agent to start with SQL Server
agent. I had previously had the same schedule set for the Merge agent.
However, whenever an error occured on the network the merge agent would
report an error and stop. The system is not monitored frequently by the
customer so I need the agent to restart/continue. I changed the schedule
for the merge agent to run once a minute. This solved the immediate
problem. However, I seem to have a similar problem on the snapshot agent
where it fails and won't restart. I ran the snapshot agent manually and the
replication picked back up. I am leery of scheduling it to run periodically
(once a minute) due to overhead. I am new to replication so I am not sure
what is a good combination for scheduling merge replication where the agents
need to report errors and continue attempting to replicate. Is there any
way to have these agents run continuously and restart after an error? Any
suggestions would be appreciated.
TIA
relax. Schedule the snapshot agent to run every minute, hour or whatever
schedule you think is best.
The snapshot will only be generated if a subscriber needs one. Otherwise the
agent will very gracefully quit and go back to sleep.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Mike M." <nospam@.someplace.com> wrote in message
news:uuE5gPi4EHA.1260@.TK2MSFTNGP12.phx.gbl...
>I am using SQL Server 2000 on Windows 2003 Server. I have two identical
> machines running this configuration. Machine A is primary, machine B is
> backup. I have setup a merge replication as such: Distributor running on
> B,
> publisher on A, pull subscriber on B. These machines are installed at a
> customer site on a new network that exeriences outages and errors. I
> currently have the schedule for the snapshot agent to start with SQL
> Server
> agent. I had previously had the same schedule set for the Merge agent.
> However, whenever an error occured on the network the merge agent would
> report an error and stop. The system is not monitored frequently by the
> customer so I need the agent to restart/continue. I changed the schedule
> for the merge agent to run once a minute. This solved the immediate
> problem. However, I seem to have a similar problem on the snapshot agent
> where it fails and won't restart. I ran the snapshot agent manually and
> the
> replication picked back up. I am leery of scheduling it to run
> periodically
> (once a minute) due to overhead. I am new to replication so I am not sure
> what is a good combination for scheduling merge replication where the
> agents
> need to report errors and continue attempting to replicate. Is there any
> way to have these agents run continuously and restart after an error? Any
> suggestions would be appreciated.
> TIA
>
|||That sounds good. Does the subscriber specify it needs a snapshot using the
synchronization transaction at the distribution database or something? I
don't wan't to add to the network traffic by having the publisher bulk copy
all the data to the distributor (machine B) if it is not needed. Will the
snapshot agent log show that it ran and did not generate any data? I'll
give that a try.
Thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e02jkqq4EHA.1452@.TK2MSFTNGP11.phx.gbl...
> relax. Schedule the snapshot agent to run every minute, hour or whatever
> schedule you think is best.
> The snapshot will only be generated if a subscriber needs one. Otherwise
the[vbcol=seagreen]
> agent will very gracefully quit and go back to sleep.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
> "Mike M." <nospam@.someplace.com> wrote in message
> news:uuE5gPi4EHA.1260@.TK2MSFTNGP12.phx.gbl...
on[vbcol=seagreen]
schedule[vbcol=seagreen]
agent[vbcol=seagreen]
sure[vbcol=seagreen]
any[vbcol=seagreen]
Any
>
|||After further review, did I mention that I allow anonymous subscriptions?
When I set the snapshot agent to run once a minute it generates a full
snapshot each time. I am going to disable anonymous subscriptions and see
how that affects it.
"Mike M." <nospam@.someplace.com> wrote in message
news:uhZYeAs4EHA.4092@.TK2MSFTNGP14.phx.gbl...
> That sounds good. Does the subscriber specify it needs a snapshot using
the
> synchronization transaction at the distribution database or something? I
> don't wan't to add to the network traffic by having the publisher bulk
copy[vbcol=seagreen]
> all the data to the distributor (machine B) if it is not needed. Will the
> snapshot agent log show that it ran and did not generate any data? I'll
> give that a try.
> Thanks.
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:e02jkqq4EHA.1452@.TK2MSFTNGP11.phx.gbl...
> the
identical[vbcol=seagreen]
is[vbcol=seagreen]
> on
a[vbcol=seagreen]
agent.[vbcol=seagreen]
would[vbcol=seagreen]
the[vbcol=seagreen]
> schedule
> agent
and
> sure
> any
> Any
>
|||Pull subscription, not anonymous. Snapshot agent set to run each minute.
Same result. The snapshot was generated each minute.
"Mike M." <nospam@.someplace.com> wrote in message
news:uJXn7Vs4EHA.524@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> After further review, did I mention that I allow anonymous subscriptions?
> When I set the snapshot agent to run once a minute it generates a full
> snapshot each time. I am going to disable anonymous subscriptions and see
> how that affects it.
> "Mike M." <nospam@.someplace.com> wrote in message
> news:uhZYeAs4EHA.4092@.TK2MSFTNGP14.phx.gbl...
> the
I[vbcol=seagreen]
> copy
the[vbcol=seagreen]
whatever[vbcol=seagreen]
Otherwise[vbcol=seagreen]
> identical
B[vbcol=seagreen]
> is
running[vbcol=seagreen]
at[vbcol=seagreen]
> a
I[vbcol=seagreen]
> agent.
> would
> the
> and
not[vbcol=seagreen]
the[vbcol=seagreen]
there[vbcol=seagreen]
error?
>
|||for anonymous the snapshot generated every time the snapshot agent is run.
For named it is not.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Mike M." <nospam@.someplace.com> wrote in message
news:%23%23vIIcs4EHA.1396@.tk2msftngp13.phx.gbl...
> Pull subscription, not anonymous. Snapshot agent set to run each minute.
> Same result. The snapshot was generated each minute.
> "Mike M." <nospam@.someplace.com> wrote in message
> news:uJXn7Vs4EHA.524@.TK2MSFTNGP09.phx.gbl...
> I
> the
> whatever
> Otherwise
> B
> running
> at
> I
> not
> the
> there
> error?
>