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

Extractor

Extractor

The Extractor reads the transaction logs of the source database system, generates intermediate files, and extracts data changes such as inserts, updates, and deletes for the selected source tables, as defined in the configuration file. The Extractor can also capture some DDL changes. The Extractor writes the changes to intermediate files.
For MySQL sources, the Extractor uses the mysqlbinlog utility to read change events from the binary log.
Usually, you run the Extractor on the source system. However, you can run the Extractor on another system provided that the Extractor can access the transaction logs. For example, an Extractor that runs on Windows can parse transaction logs on an HP-UX source system. Although the Extractor parses source data efficiently, extraction performance also depends on the hardware and I/O speed for accessing transaction logs.

0 COMMENTS

We’d like to hear from you!