I had my first conflict detection with our merge replication setup. I queried the msmerge_conflict_publicationname_aspolicy table in both publisher and subscriber and found the record that was the loser? This setup is a client subscription (with first to publisher wins). So the record that "won" was the correct one.
My question is that when I selected to "remove/delete" the conflict from the Conflict GUI, it only removed the conflict record in the publisher table (msmerge_conflict_publicationname_aspolicy); the subscriber msmerge_conflict_publicationname_aspolicy still has the record.
I had to disable my conflict alert I setup b/c this record still exists in the subscriber; I thought that when I "removed/delete" the conflict it would remove the record in both places, but that is not the case. When I renabled the alert (that monitors conflicts) it still send me an email telling me there is a conflict.
Can someone let me know what needs to be done here?