I had added two new tables to our merge replication publication couple of months ago. It created the snapshot, and the agent replicated the snapshot and everything ran fine. However, today we made a change (added two new columns) to one of other replicated table from the same publication (not the tables added in beginning of the description; an altogether different table) and the replication started having deadlock issues on the subscriber. Deadlocking customer transactions.
Our merge replication agent is set to run every minute and on every execution the merge agent would try to initialize those two tables added in the beginning of the narrative and thereby causing deadlocks.
Has anybody seen a situation like this? I am not being able to explain the RCA to myself left alone the business folks.
Any help will be highly appreciated.