Replication conflicts when only one node is updated
I have a Peer to Peer transactional replication topology in which the database from one node is never changed by the application. The second node is simply a hot backup, but there is no application connected to it. From time to time, I see update/update replication conflicts. The data is identical on both sites, but the conflict is still being recorded. With only one database being actively written to (except for replication), how is that possible?