Quick question.

Merge replication with pull subscriptions. What happens if the
synchornization is interrupted?

Does it rollback what's happened?
Can a synchronization follow that picks up where it left off?
Or, does it require a reinitalization?

I can't find anything in BoL or Google that documents what happens.

It's important for us to consider this during our design phase to determine
whether this will work for us.

Thanks.

Merge replication is "transactional" in nature. In other words it will pick
up where it left off.

However, I am unsure what you mean by synchronization. If you mean applying
the snapshot, no, if the snapshot application is interrupted, you will have
to apply the entire snapshot again. If you mean when the merge agent runs
after the snapshot has been applied and the merge agent is merging changes,
yes, this will pick up where it left off.

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"pjsm" <pjsm (AT) discussions (DOT) microsoft.com> wrote

Hi,

We have a similiar problem. The subscriptions we have created are all pull
Subscriptions. We are using Merge Replication.
Replication with each subscriber occurs once every 24 hours. This
replication occurs over and expensive satellite ISDN line.

Our problem we are facing is as follows:

The server (publisher) is set to only allow connections for 60 minutes,
however one of the subscribers is going over this 60 minute timeout. So
everyday the 60 minute timeout is being reached and the connection between
the subscriber and publisher is severred. Am I correct in understanding
that the rows transferred between the publisher and subscriber would not be
rolledback due to a connection drop and that when they synch up again the
publisher and subscriber will resume where they left off.

The reason why am I am asking this is because each time the limit is reached
approximately the same amount of data is sent and received and the amount of
data being sent each time is very high, each synch up 32 mb of data is sent
before 60 minute timeout. This makes me think that the transactions are in
fact being rolled back.


Another off topic question: How does the "Number of days before
subscription expires" setting affect performance of thsi type of
replication. I have set this setting to 60days for each of our 5
subsribers.


Any help anyone can offer would be greatly appreciated.

Thanks in advance
Warren

"Hilary Cotter" <hilary.cotter (AT) gmail (DOT) com> wrote