Transaction Replication
•Send the content published on all the publishing servers after the replication is enabled to the subscription server Upon modification;
•Data changes will be applied to the subscription server according to the order they occur on the publishing server and the transaction boundary;
•Transaction consistency can be ensured within the release;
Snapshot replication
•Distribute data in the instantaneous state at a specific time, without monitoring data updates;
•When a synchronization occurs, a complete snapshot is generated and sent to the subscription server;
Merge and copy
•Generally, snapshots of database objects and data are released, and triggers are used to track subsequent changes and architecture modifications made on the publisher and subscription server;
•When the subscription server is connected to the network, It synchronizes with the Publishing Server and exchanges all the lines that have changed between the publishing server and the subscription server since the last synchronization;