Single-master (primary-to-secondary) replication v7

Replication Server performs primary-to-secondary replication when a single-master replication system is implemented. The publication is the master and the subscription is the secondary. In a primary-to-secondary relationship, changes are propagated in one direction only, from the master to the secondary.

Generally, don't make changes to the definitions of the publication tables or the subscription tables. If such changes are made to the publication tables, they aren't propagated to the subscription and vice versa unless the DDL change replication feature is used as described in Replicating DDL changes. If changes are made to the table definitions without using the DDL change replication feature, there's a risk that future replication attempts will fail.

Don't make changes to the rows of the subscription tables. If such changes are made, they aren't propagated back to the publication. If you make changes to the subscription table rows, it's likely that the rows will no longer match their publication counterparts. There's also a risk that future replication attempts will fail.