![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Suppose I delete a record in a database at 12pm. And one staff modified the same record in another database at 1 pm. Aftere the merge replication, does that record still in both databases or not. |
#3
| |||
| |||
|
|
By default a row deleted at the publisher will be replicated to all subscribers as a delete. The updated row on the subscriber would be logged as a delete. A delete originating at all subscribers would be logged as a conflict and be replaced with an update flowing from the subscriber. If a row was deleted at a subscriber and then updated at another subscriber the first one in would remain, and the later one would be rolled back and logged in the conflict table. -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com "Man Utd" <alanpltseNOSPAM (AT) yahoo (DOT) com.au> wrote in message news:%23oN$CLqKGHA.140 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Suppose I delete a record in a database at 12pm. And one staff modified the same record in another database at 1 pm. Aftere the merge replication, does that record still in both databases or not. |
![]() |
| Thread Tools | |
| Display Modes | |
| |