快照复制使用（Snapshot replication usage）.docVIP

快照复制使用（Snapshot replication usage） Snapshot replication is a magic weapon in which data and database objects are replicated and synchronized between databases to ensure consistency between multiple databases. In short, snapshot replication is the process of implementing data transfers from one database server to one or more geographically distinct database servers. In fact, for snapshot replication, we can make an image of the metaphor. It is a process of taking pictures of a database and transferring it to other databases at a time when a database administrator is setting up. In this way, data synchronization between databases can be guaranteed. Typically, snapshot replication has the following characteristics. First, from the term snapshot, we can see that the photo is a static process, that is, only reflects the status of the database at a certain moment, but will not reflect a change process of the database. Snapshot replication copies data at a set time of a database without continuous monitoring of data changes over a period of time. This is essentially different from another brother, transactional replication. If snapshot copy is compared to full backup, transaction replication is a differential backup. Two snapshot replication, the required resources are relatively large. Snapshot replication is the replication of the entire database, regardless of whether it has changed. Undoubtedly, this replication time, transmission time will be relatively long, and its consumption of server and network resources will be more. Therefore, the cost of snapshot replication is relatively high. However, snapshot replication can improve efficiency in certain situations. For example, it is reasonable to use snapshot replication to coordinate data consistency between multiple databases, as for data that does not change frequently, or does not require high synchronization. Snapshot replication is a more advanced technology, but it is not in all application scenarios, it can play