Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Stages of Replication Processing

Stages of Replication Processing

Replication processing consists of multiple stages. For example, in a topology that runs a Server Manager instance on the source system and on the target system, replication processing occurs in the following stages:
  1. The Extractor captures changes from the source database and writes the changes to intermediate files. Then the Extractor sends a message to the Server Manager on the source system that confirms the extraction stage is complete.
  2. The Server Manager instance on the source system notifies the Server Manager on the target system that the intermediate files are ready to be transferred.
  3. The Server Manager instance on the target system uses HTTP or HTTPS to get the intermediate files and then sends a message to the Server Manager on the source system to confirm that the files were transferred.
  4. The Server Manager instance on the source system removes the intermediate files that were transferred to the target.
    For replication jobs with multiple targets, the Server Manager instance waits until the intermediate files have been transferred to all of the targets.
  5. The Applier applies the changes from the intermediate files to the target database. When apply processing is complete, the Applier sends a confirmation message to the Server Manager instance on the target. The Server Manager purges the intermediate files for which all changes were processed and retains only the intermediate files that contain uncommitted transactional changes.

0 COMMENTS

We’d like to hear from you!