Is there a way I can figure out why transactional replication had the status "stopped" (according to Replication Monitor)? The latency column in the monitor showed a value of 08:47:55. There are 11 subscriptions to this publication and all were stopped. Right-clicking one and selecting "start synchronizing" caused all subscriptions to start synching again.
I checked the event logs on the server (publication server) but found nothing that correlated to the time that replication would have stopped (based on latency value). Is there any way to figure out why these stopped?
This has happened twice in the last week now and I don't know where I should look other than the event logs (which did not help). ANY ideas are greatly appreciated and welcome. Thanks!