I am using merge replication with SQL 2012. I am trying to rename a published table, and rename a published field.
These operations are not permitted in merge replication.
However I can think of an action plan if these things are needed. For instance renaming a field would include,
- Adding the new field
- Migrating the data from the old field to the new field
- Wait for a while, perhaps a month
- Delete the old field
The problem is after step 2. We can force a software upgrade to the clients so that data is written into the new field.
But some data may have been modified in the old field at one of the subscribers before they do the sync which makes the schema change. This would also be before they were forced to do the update.
The migration could be done more than once, but by the time you get to step 4 its hard to know which modifications have been made to the old field, and which have been made to the new field.