Hi, I have couple of questions about replication, especially transaction replication. MSDN Says:- By design, transactional replication addresses the principal requirements for this scenario: • Transactional consistency • Low latency • High throughput • Minimal overhead I have a scenario with: Primary Server A, Secondary Server B, Network line between them currently 10MB I plan to use trans. replication to repl from A to B. As I want least data loss and max availability, can I : 1. Have publisher, distributor and subscriber on A. Also, can I replicate publisher, distributor and subscriber on B too which can be brought up in case of site A failure. I think, it is NOT POSSIBLE but would like some confirmation from someone else. 2. Another possibility is to have publisher, distributor and one subscriber on A and another subscriber on B. So, when Server A fails, application can connect to DBs on server B. Another question is, my approx. transaction size is about 50KB. is it possible to estimate(even roughly) how much bandwidth will be adequate to keep latency lowest? Thanks a lot!!!...any help is appreciated.
Having Only two Servers say A AND B.You can set up replication as follows. You can Configure server A as the Publisher and act as it own Distributor.Then configure Server B as the Subscriber. Steps are as follow. - First configure the Distributor on Server A. -Second, configure the Replication on Server A. -Third, configure the subscription. use this as a guide: