January 11, 2013 at 12:11 pm
I am just learning about replication, as I have been asked to set up a merge replication for one of our databases. Besides being completely overwhelmed by the whole thing :unsure: I do have a question that I cannot seem to find an answer for.
The database I plan to set up replication for has several SQL Agent jobs that add/update/maintain the data within the tables. How are Agent jobs handled with merge replication? Are jobs on both the publisher and the subscriber, or do they run only on the publisher and then the data is updated when synchronization occurs?
As a side note - I have learned lots from the Stairway to Replication by Sebastian Meine. Excellent reading – and for a newbie like me, written in language I can understand. Kudos to Sebastian!
February 7, 2013 at 11:09 am
Data modifications done by an agent job are handled the same way any other modifications are.
February 7, 2013 at 8:12 pm
As far as merge replication is concerned, the SQL Agent Jobs that are updating data are no different to any other client application that is updating data. All that merge replication cares about is whether an INSERT, UPDATE or DELETE has occurred - not what process caused the INSERT/UPDATE/DELETE to be done. It also doesn't care which database is modified. Merge replication will make the equivalent changes to all other databases it knows about.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply