We have a republishing merge replication setup of SQL Server 2005 Head Office (HO) publishing to SQL Server 2005 Regional Offices (RO) re-publishing to SQL Server 2005 Express Stores (ST). The problem we are having is that of strange conflicts. They can
be grouped into the following types:
1) Update conflicts where the data is the same on both sides and one side hasn't made a change since the last replication event.
2) Delete/Update conflict where the delete is real but the update isn't. Like #1 the update never occured.
3) Delete/Delete confluct where one of the deletes are real but the other isn't which then create a Unique identifer error in the conflict resolver.
We have looked over the SQL Server CU's both nothing describes our problem as we are running SP3. We've also search for other reported problems and can confirm that we don't have filters on DateTime fields only GUID fields and the join filter table hierarchy
isn't deep. We've also tried a re-initialisation and verified that the collation is the same over every SQL instance.
Has anyone also come across and found a solution for this?
View Complete Post