SQL Server Replication – Understanding Why Replication Distribution Agent Stops

sql serversql-server-2008-r2transactional-replication

Let me preface this in that I'm working as an accidental DBA at the moment.

We have continuous transactional replication running. For some reason the Distribution Agent stops with a message of "success", but I can't understand at all why it is stopping and from the logs I don't get much information.

Two questions.

  1. Other than looking at the monitor does anyone have some good ideas as to where I can get a bit more detail? I can do verbose logging to a file but the replication has lots of data and the files grow really big really fast.

  2. Is there a way to have the Distribution Agent restart itself whenever it stops other than when I manually stop it? Maybe adding an additional step to the Agent job?

Best Answer

As far as starting it...add a schedule that runs the job every minute. If the job is running, no issues. If not, it will start.

can't help on question 1 with no additional info.