We have peer to peer replication configured in SQL 2014.Often we are seeing that the replication is getting failed with an error that a particular column on subscriber database is invalid. when we compare it manually with the publisher database, its obviously present there.Then we end up creating the column manually and replication catches up there afterThen after a few days, this happens for a different table and a column. we are unable to fix this totally at once.This is a 2TB database and we are scared to re initiate entire replication process.What could be the potential problems:1. Could the new column be introduced in the publisher newly which isnt getting pushed to the subscriber. Creation/modification of an object is a DDL operation. will peer to peer replication push DDL operational changes?2. Could some user/process be deleting these columns on the subscriber database? Is there a way to check that?
↧