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 - 2002-05-21 : 09:11:54
|
| Brian writes "Hello,Here is my scenerio: I will be using SQL 2000.Server 1 is at location AServer 2 is at location BApplication X is installed at both locationsApplication X1 (the app at location 1) can modify data on Server 1 and Server 2.Application X2 (the same app at location 2) can modify data on Server 1 and Server 2.I have to get both databases to be identical to the other database. As long as data is qued up and no data is lost I don't mind latency. In face there may be times that the two systems will be out of contact with each other for hours( not often though).I need to have both databases merge and have the same data. I do know that all reacords inserted into server 1 will have identifiers indicating that this record was inserted into server 1 and the same goes for server 2.What type of "bi-directional" replication can be done? I know it will involve merge replication but do you have any suggestions on what to do and more importantly on what not to do? Do you know where I can find good resources on begining replication with SQL 2000? Thanks" |
|
|
DavidD
Yak Posting Veteran
73 Posts |
Posted - 2002-05-27 : 01:43:09
|
| Brian, SQL Server merge replication could work in this scenario, but you have to be aware of its limitations.1. Once it is set up you are very resticted in how you can alter your tables, so don't expect to make on the fly changes to your system.2. Any problems (eg distibutor goes bung) means you usually have to start from scratch.3. It uses plenty of overhead, so make sure you have a fast connection between sites. Do not use phone lines.regardsDavid |
 |
|
|
|
|
|
Merge and Bi-Directional Replication