I have a situation that I am looking for some guidance on.
I have 4 SQL 2008 databases that are syncronized over the internet using merge replication. 1 publisher and 3 subscribers.
Normally records that are entered on a databases are also only updated from that same database and everything works fine. However, sometimes an update is made at the publisher to a record that was created at the subscriber and can cause a conflict if the same record was updated on the subscriber since the last synchronization (usually 60 seconds).
I have used the conflict resolver built into SSMS and that works fine for me (I understand the schema and underlying data). However, I am looking for a solution where an end user (someone in management) can be alerted of a conflict when it happens and resolve the conflict without any intervention from me in a way that they can understand?
What have others done when having to handle replication conflicts?