One thing we need to be sure of is that the subscriber and publisher “look” the same. This is from the DBA point of view. Are all aspects of the table the same at the subscriber?
We seem to be able to control this in the article properties. The defaults say that the FKs, Indexes, Triggers, Defaults etc go to the subscriber:
There is a related setting on the subscriber properties for the publication that says we want to replicate schema changes – by default set to true:
However, note that after initialization when we make a change on the publisher, not everything will go down. We can see what is ready to go in sysmergeschemachange. For the main changes we need to remember:
- Replicated to the Subscriber: Primary Keys, Foreign Keys, Check Constraints, Default Constraints
- Not Replicated to the Subscriber: Indexes, Triggers
So – be careful to manually keep the subscriber in sync when it comes to indexes and triggers!