We'll be implementing replication soon but we have some concerns in the case
of disaster recovery.
My question revolves around the transaction log on the publisher.
Setup
Remote Distributor
Transactional Replication
If we found ourselves in a situation where the remote distibutor fails, what
impact does that have on the transaction log of the database being published?
Do the transactions that failed to get moved to the distribution server get
stuck in the TLog preventing a truncation of the Log. This would just be a
worse case scenario. We're concerned about anything that could happen and
cause an adverse affect on the performance and/or size of the Tlog.
>> Stay informed about: Transaction Log