merge replication, what hapens if...

We have 2 SQL2000 servers updating in real-time using merge replication. I need to shut one server down over this weekend, but the other one needs to remain up. What will happen? Will we have to replicate all the data all over again or will it pick up where it left off?

If I'd have to re-replicate everything, can I prevent this by stopping a service or setting a replication schedule instead or something?

Thanks for your help,
Erica <-- not a SQL AdminIt will pick up from where it left of when you shut it down. You may receive some errors in your system log.

Merge replication real-time monitoring

Hi,
So far I used merge ActiveX control to start and monitor pull merge
subscription within C# client application. Due to fact that some subscriber
machines are rather slow and publication is relatively complex (lots of join
filters etc.), I want to offload processing to distributor. Some subscribers
often report "The process is running and is waiting for a response from one of
the backend connections".
Since I cannot control offloading with ActiveX (because it starts process on
local subscriber, or I am missing something here?), I would like to
use -Offload, start agent using msdb..sp_start_job on subscriber and monitor
replication progress by directly reading distributor's
distribution..MSmerge_history.
My questions are:
- is there better approach to accomplish same goal (e.g. .NET Remoting?)
- how to get "percentage complete" (agent outputs it if -OutputVerboseLevel 2
is used, but how to get it from subscriber?)
Links with more detailed info on replication would also be nice :-)
Thanks,
Tom
for percentage complete have a look at the status event.
The replication ActiveX controls do not support the full range of properties
that the SQL DMO replication objects support. IIRC the offloadagent
parameter is ignored in the merge ActiveX control.
"Tom" <tomislav.hrvoic.rimuv.dis@.inet.hr> wrote in message
news:%23ouVBHUJEHA.2660@.TK2MSFTNGP09.phx.gbl...
> Hi,
> So far I used merge ActiveX control to start and monitor pull merge
> subscription within C# client application. Due to fact that some
subscriber
> machines are rather slow and publication is relatively complex (lots of
join
> filters etc.), I want to offload processing to distributor. Some
subscribers
> often report "The process is running and is waiting for a response from
one of
> the backend connections".
> Since I cannot control offloading with ActiveX (because it starts process
on
> local subscriber, or I am missing something here?), I would like to
> use -Offload, start agent using msdb..sp_start_job on subscriber and
monitor
> replication progress by directly reading distributor's
> distribution..MSmerge_history.
> My questions are:
> - is there better approach to accomplish same goal (e.g. .NET Remoting?)
> - how to get "percentage complete" (agent outputs it
if -OutputVerboseLevel 2
> is used, but how to get it from subscriber?)
> Links with more detailed info on replication would also be nice :-)
> Thanks,
> Tom
>
sql