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

Overriding the Applier Settings for a Target

When you configure a replication job that has multiple targets, you can override some Applier settings for a target.
The following types of settings can be overridden for a target:
  • The apply mode
  • The schema name for Merge Apply audit log tables on the target
  • The name of the recovery table in the target database
  • The location of the log file that is used for conflict resolution
  1. On the
    Routing
    tab, select the target server for which to override settings and click the
    Override Apply
    subtab.
    The following image shows this subtab:
    Override Apply subtab on the Routing tab
  2. To select another apply mode for the selected target, click one of the following options In the
    Replication Type
    list:
    • SQL Apply
    • Audit Apply
    • Merge Apply
    You can use Audit Apply mode for a secondary target to add audit log tables in the primary target database that use the same schema as the regular target tables in the same database. In this case, the primary target and secondary target use database connections with the same connection information. To create valid SQL statements for the audit log tables for the secondary targets, set the
    apply.force_log_table_suffix_for_audit
    advanced runtime parameter to 1. Also, ensure that the names of the audit log tables end with the suffix that is specified in the
    Log table suffix for merge apply
    field on the
    Runtime settings
    tab >
    Calculated Columns
    view.
  3. To change the schema name for audit log tables on the target, enter a schema name in the
    Log table schema
    box.
  4. To change the recovery table name, click the
    Browse
    button for the
    Recovery table name
    field.
    Then, enter the database, schema, and recovery table name in the appropriate fields and click
    Yes
    .
    For
    Cloudera,
    Flat File,
    and Hortonworks
    targets, skip this step. These target types do not use a recovery table.
    When you later start the Applier, it generates the recovery table on the target.
  5. To override the path to the log file that the Applier uses for conflict resolution, click the
    Browse
    button for the
    Conflict logging path
    field.
    The Applier logs data conflicts that occur during apply processing to this log file.
  6. Click
    Save
    .

0 COMMENTS

We’d like to hear from you!