Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2001-01-31 : 21:27:22
|
Jay Natarajan writes "Hi:
What have a project that will consist of 3 production servers in 3 different regions and each server has it`s own clients in that region. We want to use replication to keep them all in synch so that if one goes down, the client PC`s would just re-connect to one of the other two remaining servers and keep working.
1. I am wondering what type of replication to use? 2. I was leaning towards merge, but was wondering how to use it to keep 3 servers in synch? If I use the Central publisher with updating subscribers scenario, I foresee a potential problem as follows:
A. Server1 is central publisher B. Server2 and Server3 are updating subscribers C. Server2 (or Server3) goes down, clients reconnect to Server1 and keep working. D. When Server2 (or Server3) is back up, Server1 will push all changes back to Server2.
but, E. Server1 goes down, clients reconnect to either Server2 or Server3 and keep working. F. Since Server1 is down, changes made to Server2 not replicated back to Server3 (The central publisher is gone) until Server1 comes back up. G. Server2 goes down while Server1 is down, clients re-connect to Server3. H. The changes made to Server2 were not replicated to Server3 because the central publisher is missing. I. Server3 therefore is missing data changes.
Please help me figure this out. I feel as if I am missing something that I could do to also keep Server2 and Server3 in synch with each other besides the Central Publisher.
Thanks in advance
Jay Natarajan" |
|
|
|
|
|