Two-way replication conflict example

WIth 2-way replication there is more chance of getting conflicts than with 1-way replication. This is because both sides are being updated in real time. 

By way of the following example, it is demonstrated how Dbvisit Replicate can assist with conflicts in 2-way replication.

Example:

We have 2 databases in our 2-way replication. Database A and Database B.

We have the following table with the same data in both databases:

Table TOLL.TOLL_ZONE

Id  Name      Update_date

--  --------  -----------------

1   Lane 1    10/10/2012 23:00

2   Lane 2    09/10/2012 21:00

Now the following scenario happens:

1. 2-Way replication is configured between table TOLL_ZONE in Database A and Database B
2. Both tables are in sync
3. Communication between database A and database B breaks and Dbvisit Replicate is no longer able to replicate changes
4. Record with id=2 is updated on database A and database B with different values:

5.  

   DATABASE A

   Table TOLL.TOLL_ZONE

   Id  Name      Update_date

   --  --------  -----------------

   1   Lane 1    10/10/2012 23:00

   2   Lane 222  12/12/2012 09:45  <== Updated

   DATABASE B

   Table TOLL.TOLL_ZONE
   Id  Name      Update_date
   --  --------  -----------------
   1   Lane 1    10/10/2012 23:00
   2   Lane 200  12/12/2012 10:10  <== Updated latest

6. Communication is restored
7. What will happen to the replication?