Suggestions when changing the design of a replicated database

Microsoft Replication Manager

Suggestions when changing the design of a replicated database

  • Synchronize all replicas in the replica set before making design changes.

  • Check all replicas to make sure that the name you are selecting for a new field or object isn't already being used as the name of a local object. (If you do choose the same name, the local object will be renamed.)

  • Don't create relationships between tables when you intend to replicate some tables but keep others local.

  • Make sure that the number of bytes you add to a field or the number of fields you add to a record doesn't exceed the maximum size for a replicated database. For more information on the size limitations of a replicated database, click .

  • If you use linked tables, keep in mind that linked tables aren't automatically replicated. If you create a linked table in the Design Master, it's created as a local object and remains local until you make it replicable. When you make the table replicable, the link and the table are sent to all the replicas in the set. After the table appears in each replica, you can change the link in an individual replica or in the Design Master without affecting the other members of the replica set. To refresh the link in all members of the replica set, change the replicable linked table to a local table (in the Design Master), refresh the link, and change the table back to a replicable table.