As a developer who has for the first time successfully implemented a replication topology for our production database, I'm monitoring it very closely and fretting over potential problems.

I'm pleased that the Log Reader Agent has been running for 2 days 20 hours 6 minutes and 2 seconds and don't want to get ahead of myself (as I know that problems will come) but how large will this figure get?

Do dba's ever restart the log reader agent if it's been running for 30, 100 or 365 days? Is this beneficial or is there a website where I can submit a snapshot of Log Reader Agent status if it ever hits 2 years without a problem? (Presuming we have no server reboots - which if course we will).



I think it depends on your environment and how busy it is but I support quite a few environments that are very stingy with their patches because they have incredibly low surface areas and end up with reboots/SQL restarts pretty infrequently (a few times a year) and the log reader agent isn't restarted outside of this schedule and there are no issues.

If your environment is high transaction and you are experiencing issues with the cleanup jobs on distribution and are running a local distributor you may see a benefit from restarting but, in general, I have found no need to worry about restarting the log reader agent.

I don't believe Microsoft has any particular guidance so this is a YMMV type of question but I think you'll be fine to not restart it outside of your normal patching and reboot/restart policy. As long as you monitor performance and look for issues and symptoms with your replication environment you'll be fine IMHO.

  • Great that's what I wanted to hear, cheers Mike. – David A Gibson Nov 1 '11 at 16:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.