all groups > sql server replication > march 2006 >
You're in the

sql server replication

group:

Theory Question - Logreader Resiliency


Theory Question - Logreader Resiliency sqldood NO[at]SPAM googlemail.com
3/19/2006 1:18:27 PM
sql server replication:
If the logreader process stops, the server dies for example, and while
it is not connected to the publisher transactions occur with the
published database, will those transactions be lost, or will they be
replicated by the logreader the next time it connects to the published
database?

Im thinking that because transactions are flagged for replication in
the transaction log, these remain until the logreader has replicated
them to the distribution server - and un-set the flag. Am I correct?
Re: Theory Question - Logreader Resiliency Hilary Cotter
3/19/2006 9:08:08 PM
They remain in the log until the log reader has read them, and the log is
backed up. The sequence is they are written to the log and marked for
replication, the log reader reads them and puts a marker in the log saying
it read those transactions. Then and only then when the log is dumped will
the VLF be marked for reuse.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



[quoted text, click to view]

AddThis Social Bookmark Button