Snapshot Replication
1 like441 views
Snapshot replication distributes data as it appears at a specific time, without monitoring updates, and requires the entire snapshot to be sent to subscribers during synchronization. It is suitable when data changes infrequently, and the latency in synchronization is acceptable, particularly for small datasets. While it has lower overhead compared to other replication methods, large datasets can demand significant resources for snapshot generation and application.
Snapshot Replication
- 2. Introduction Agents required When to use Pros n Cons Implementation with an example • Q&A
- 3. Snapshot replication distributes data exactly as it appears at a specific moment in time and does not monitor for updates to the data. When synchronization occurs, the entire snapshot is generated and sent to Subscribers.
- 4. Snapshot agent creates the snapshot of the publisher. Distribution agent applies the snapshot to the subscribers.
- 5. Data changes infrequently. Latency in synchronization of data between publisher and subscriber is acceptable. Thesize of entire data set being replicated is not very large.
- 6. Pros- Snapshot replication has lower overhead on publisher than transactional/merge replication because incremental changes are not tracked. Cons - If the dataset being replicated is very large, snapshot replication requires substantial resources to generate and apply the snapshot.