Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are running a scheduled agent which updates every single document in a very large database. Is it a good idea to keep replicator running whilst every single document is updated via the scheduled agent?

Any tips or advice would be appreciated, thank you.

share|improve this question
up vote 1 down vote accepted

Well: when replicator runs, it takes a kind of "snapshot" of things to do and works on them. That said, it will not be a problem, to run both tasks simultaneously, but might cause some disk io peaks.

I would recommend to schedule replication after the agent run, to not have to much performance impact on the server.

And I would check,if it really is necessary to change ALL documents in that database on every agent run, as usually this is just because of some lazyness of programmers and not very often really is necessary...

share|improve this answer
Thanks Torsten for your response. This was a one time agent in a large database with 1.5 million documents where the change affected all documents (data cleansing). I was advised that small bursts of replication might be better than trying to sync 1.5 million documents all at one time, but was not really sure if this would affect the agent at all. – pipalia Apr 1 '14 at 8:55

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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