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-02-20 : 09:16:49
|
| paul writes "I am working with SQL Server 7, sp3. I have four instances of a database in 2 cities. There is a merge replication job on Table_1. Table_1 receives inserts at all 4 boxes, and inserts on Table_1 fire a trigger which does a delete and insert on Table_2. Previously one database has been a primary, and I have replicated Table_2 by hourly snapshot. I now want to make each database independent and capable of saving Table_2 data from client connectionsMy question is how do I ensure that changes to Table_2 caused by the Table_1 trigger remain consistent across the 4 boxes at the same time as direct client inserts to Table_2 are merged? Should I have the trigger on only one box and do a merge of the 4 Table_2 instances? I can't quite make the leap to see if this is what I want, or if I should have the trigger on all 4 tables.I've spent some time with google on web sites and newsgroups on this question, but the issues continue to remain opaque. Any de-muddying of the waters you might offer would be greatly appreciated.Thanks and Regards,Paul" |
|
|
|
|
|
merge replication, triggers