April 24, 2003 at 12:57 pm
Did any body tried active-active (two way) replication. That means keeping both the DB server in synch. My app is high transaction processing, is it ok to set up such replication. I appreciate your response.
April 24, 2003 at 1:52 pm
If you mean a republicataion topology in wich the subscriber is also a publisher and the publishger is also a susbcriber it is no problem. That schema is the one I have with multiple susbscribers and publisher.
If some articles are going to be part of both publication (in both directions), check the @loopback_detection option in the sp_addsubscription stored procedure. That will prevent transactions to travel for ever in both directions.
April 24, 2003 at 2:01 pm
Thanks for response. I am more worried about the conflicting policy of replication. My App is generating unique key based on certain parametere, in case same key is generated in both th DB than definitely one will be problem.
Here I am talking about complete DB replication not one or 2 article.
April 24, 2003 at 2:15 pm
Same problem regardless of number of articles. Both merge and transactional with updates support identity key ranges. If you're building your own id's then you have to build in a mechanism to keep them unique.
Andy
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply