November 5, 2016 at 11:32 am
Hi,
We are considering replicating a subset of tables to multiple subscribers in order to offload Read Traffic from the main production db. The application will never directly update the subscribers.
Are there any downsides to this approach?
Thanks!
November 8, 2016 at 6:57 am
Im assuming u want to use transactional replication and have date in real time on subscribers?
If yes, then it is one of the best solutions to offload data for reading purposes.
There are few things u need to consider.
Remote or local distribution? Distributor will need some resources to run distribution/logreader/snapshot agents. I would suggest to user remote distributor and not add any more stuff to your production system.
Pull or Push? In your case probably you should go with pull (distribution agent will be located on each subscriber). However from my experience it is bit harder to manage replication. On other hand if u will have separate instance for distributor you can locate all your agents on that remote distributor (also depends what resources u will have on that distributor)
if mirroring is used on published db? IF mirror will be behind (by any reason) then your log reader and your replication will also fall behind
BartL
Replication Blog
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply