Logreader down question

If the logreader stops (separate distributor server from publihser) and
cannot connect to the publisher for - let's say - 4 hours, is that data lost
or will the transactions to be replication still be in the tlog? and
replication will catch up - in total (including the 4 hours down)?
Just to clarify...
The Transaction Retention period is the default 72 hours in the Distribution
properties. ?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:28c201c51dbe$9111c5e0$a601280a@.phx.gbl...[vbcol=seagreen]
> 4 hours shouldn't be a problem.
> Firstly, the commands won't be removed from the log until
> they have been read by the log reader, so they'll remain
> there.
> The time that this can be an issue is if 4 hours is
> longer than the transaction retention period. If this is
> the case, the distribution cleanup agent can remove
> commands before the distribution agent propagates them,
> in which case you'll end up having to reinitialize to
> recover.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
> publihser) and
> hours, is that data lost
> the tlog? and
> hours down)?
|||Yes - if you have the default of 72 hours, then you're
fine
Rgds,
Paul Ibison
sql