June 23, 2008 at 6:46 am
Hi all,
We have two offices one in pune and other one in mumbai.
mumbai users will be performing read only operations from mumbai server and write operation in Pune Server. Our primary server will be in Pune.
Pune users will be performing read and write operation in Pune server(local db).
both primary and secondary database will be synchronized as per the architecture we select. either we would be going for merge replication(as secondary database would be accessible even if it is online) or transactional replication with updatable subscription(Bidirectional).
what would be the possible risks if the link between primary and secondary server goes down, will synchronization result in possible loss of data in any of the topology we follow, or there won't be any?
and second thing Merge Replication or Transactional Replication with updatable subscription would satisfy our needs and requirement.
which topology best suites our requirements or other if it is required. please suggest
thanks
vinit
June 23, 2008 at 4:14 pm
Go 4 transactional replication only if consistent or reliable network connection is there. Merge replication is better suited for mobile users or field salesman scenario based situations.
Manu
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply