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

Applier Processing of Updates for Duplicate Records

Applier Processing of Updates for Duplicate Records

If mapped source and target tables contain duplicate records, the Applier processing of Updates for these duplicate records depends on the apply mode.
  • In Audit Apply mode, the Applier processes Updates for duplicate records correctly.
  • In Merge Apply mode, the Applier ends with an error when processing Updates for duplicate records.
  • In SQL Apply mode, the Applier processing of Updates for duplicate records depends on whether the updated columns are part of a virtual index:
    • If the updated column in duplicate records is part of a virtual index, the Applier updates all of the target duplicate records.
    • If the updated column in duplicate records is not part of a virtual index, the Applier always updates only one of the target duplicate records. This behavior results in data inconsistencies.
    To avoid data inconsistencies between the source and target tables that might contain duplicate records, add a virtual index for the source columns that might be updated on the source.

0 COMMENTS

We’d like to hear from you!