Replication internals...

Hi,
I need to answer a question for management and I have little replication
knowledge. I'd appreciate any input here.
What happens to the dbs on either side i.e. dist and subscriber, when in the
middle of the operation, one of the systems crashes? vs. what happens when
you click the stop sync button? How do you recover both in the event of the
former assuming the stop synch does not separate, but controls, parent from
children records.
Thanks much!
replication stored the last recorded transaction in the meta data tables on
the subscriber and the publisher\distributor.
When the system comes back up the data will be replayed to the Subscriber
provided it has not being cleaned up on the publisher\distributor.
Transactions are applied on the subscriber within a transactional context.
If you are replicating data which is part of a pk-fk relationship these
commands will be replicated as past of a transaction - unless you are not
enforcing the relationship for replication.
So it is very much like the ACID properties you see when you apply the
transaction on the publisher.
If the distribution database is corrupted its all bets off, as it holds the
transactions to be applied on the subscriber.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"JimMac" <JimMac@.discussions.microsoft.com> wrote in message
news:5BF14F6D-AB6E-4CB6-AC8E-125F43FFE652@.microsoft.com...
> Hi,
> I need to answer a question for management and I have little replication
> knowledge. I'd appreciate any input here.
> What happens to the dbs on either side i.e. dist and subscriber, when in
the
> middle of the operation, one of the systems crashes? vs. what happens
when
> you click the stop sync button? How do you recover both in the event of
the
> former assuming the stop synch does not separate, but controls, parent
from
> children records.
> Thanks much!