Reduce the Use of Replication Definitions

In a replication system containing only Adaptive Server databases, you can reduce the need for replication definitions for tables in a warm standby environment or multisite availability (MSA) environment because RepAgent for Adaptive Server uses Log Transfer Language (LTL) to specify a table or column name that may be quoted, and whether a table column is part of the table primary key.

Since RepAgent sends the primary key and quoted identifier information to Replication Server, you do not need a replication definition if the sole purpose of the replication definition is to specify primary key and quoted identifier information. The reduced requirement for replication definitions makes it easier to manage a replication environment involving databases with many tables, tables with many columns, or tables that change schema frequently. Replication performance improves for tables that are currently without replication definitions, as RepAgent directly provides Replication Server with table primary key information, so that Replication Server packs only the primary key columns in the where clauses of update, delete, and select commands.

You do not need to create a replication definition for a primary table if the sole purpose of the replication definition is to specify some or all of the following:

See Replication Server Administration Guide Volume 1 > Manage Replicated Objects Using Multisite Availability > Reduce the Use of Replication Definitions and Subscriptions to configure the replication system to reduce replication definitions.

System Requirements

RepAgent sends primary-key and quoted identifier information only with LTL version 740 or later, which is supported by Adaptive Server 15.7 and later, and Replication Server 15.7 and later.