Monitoring Transactional Replication (with pull subscribers) ! he

Have a look at the Replication Alerts for some of this -
specifically the Replication: agent failure alert.
To help troubleshoot errors, the replication history
tables (MSsnapshot_history, MSlogreader_history etc) are
used, either directly or through the GUI. Also, setting
the agents to log history to a text file can be extremely
useful and give a more granular type of error handling
capability (see http://support.microsoft.com/?id=312292).
To backup the log just do a normal backup. The log won't
be truncated of this work until the transaction has
finished and the log-reader has read the whole
transaction.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
also have a look at the msrepl_errors table in the distribution database.
Errors are logged here.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:3ce301c4e287$c466a4a0$a301280a@.phx.gbl...
> Have a look at the Replication Alerts for some of this -
> specifically the Replication: agent failure alert.
> To help troubleshoot errors, the replication history
> tables (MSsnapshot_history, MSlogreader_history etc) are
> used, either directly or through the GUI. Also, setting
> the agents to log history to a text file can be extremely
> useful and give a more granular type of error handling
> capability (see http://support.microsoft.com/?id=312292).
> To backup the log just do a normal backup. The log won't
> be truncated of this work until the transaction has
> finished and the log-reader has read the whole
> transaction.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>