I inherited a system that is setup with bi-directional replication. I have been seeing some errors for 'primary key violation' and 'row not found' on this system. I ran a validate on the subscription and have several tables that are out of sync. I can run tablediff to find the differences, but since this is bi-directional I'm not sure how to fix them.
In regular transactional replication, if a row exists on server A but not on server B, I would run an insert on server B to correct this. If I do this in bi-directional, the row will then try to be re-inserted to server A and cause another error.
This is a very large database and reinitializing has to occur with a database restore. Is there any way to fix these issues without reinitializing?
Thanks,
Kim