Load on publisher in case of PUSH replication

  • Suppose we have distributor configured separate than publisher. And we are using PUSH method for transactional replication. Then what will be load effect on Publisher, either distributor will take the whole load of PUSH or there will be some load on publisher also?

    Thanks

    DBDigger Microsoft Data Platform Consultancy.

  • When creating the snapshot the publisher places some locks to know where to start transferring transactions to the distribution database. Then the data for the snapthot has to be read.

    When replication is running the load is that the Log Reader Agent has to read the transaction log to trace changes on the published tables.

    I think that's it.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply