When deciding which replica type to use, consider the following:
- If you require the ability to create replicas in personal or file geodatabases, you must use either checkout/check-in or one-way replication. However, if you are using an ArcEditor license to edit the child replica's data, consider using personal ArcSDE as the target geodatabase. Using ArcSDE instead of your personal or file geodatabases allows you to create two-way replicas. With two-way replication, you can synchronize multiple times without have to re-create the replicas.
- One-way replication is ideal for cases where you want to publish changes from your production server to your publication server. One-way replication enforces unidirectional synchronization and doesn't require the child replica's data to be versioned if using the simple model. With a simple model, the fact that the types are simple makes the data more interoperable since it doesn't have to conform to complex ESRI data structures.
- If implementing a one-way system where you sometimes need to edit the child replica's data, consider using two-way replication. Since one-way replication assumes that the data is read-only on the child, a synchronization may overwrite edits to the child replica's data. The conflict detection logic of two-way replication will flag these differences as conflicts, allowing you to decide how to handle the differences. Two-way replication allows data exchange in both directions but also works in cases where you only send changes in one direction.