Our environment is SQL Server 2008 R2 running Merge Replication with Web Synchronization using the SQL Server Compact Edition 3.5 SP2 Server Tools, and SQL Server Compact Edition 3.5 SP2 for the client DBs on full Windows XP or later OS’s.
We have about 120 articles, each of which range from 10 published columns to close to the 255 limit. Regarding join filtering, we have a root article filtered on the hostname, which then has 2 levels of filtering cascading off that.
We are using the default Row Level change tracking.
Tracking of schema changes replication has stopped working in some of our publications
The manifestation is that subscriptions schemas are left behind at some point in time, and the only temporary recovery has been to delete the client DB and get it to recreate from a snapshot which then contains the latest schema. However, subsequent
schema changes don’t propagate.
The longer term workaround that we have applied has been to manually update the sysmergesubscriptions table on the publication DB and set the schemaversion column values (ALL of which are inexplicably high in this
View Complete Post