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 - 2000-12-13 : 00:11:07
|
mark writes "Hi
We have a database(s) (SQL 7 on NT4) that are located in three different servers. For political reasons (bless the bosses) the databases had to be up and running before a policy on sharing data was agreed.
The problem is this... in order for merge replication to work we muct have a gui ID on every table that is replicated. The problem is that there are duplicate records in each database and we need to make sure they get the same ID. I have written a loop to add the column to each table and we are planning to write a loop to copy all the data from 2 of the databases into the third. Although duplicates exist, they are read-only in two of the three (various combinations though).
The plan is that by doing it this way any key violations will prevent duplicates, once all the data is in one db then we can create the gui id columns and set up the merges with snapshots to re-populate the other two databases.
Does this sound convincing? There are two of us doing it and it's a first for both of us.
Any thoughts on the matter would be much appreciated.
cheers
Mark" |
|
|
|
|
|
merge replication