Identifying replicated transactions and procedures

In a Sybase transaction replication system, the Mirror Replication Agent and Replication Server components both provide features that allow you to identify (or select) the transactions that you want to replicate. You do not need to replicate all transactions, or all data-changing operations, in the primary database.

The ability to select transactions for replication is particularly useful when you need to implement a replication system to support an application that uses some of the tables in a database, but not all of them.

By marking tables, you identify the specific tables in the primary database for which transactions are replicated. Transactions that affect the data in marked tables are referred to as replicated transactions.

By marking stored procedures, you identify (or select) the specific procedures in the primary database that are to be replicated as applied functions. When a marked procedure is invoked in the primary database, its invocation is replicated, along with its input parameter values, to the standby database.

The ability to select procedures for replication is particularly useful when you need to implement a replication system to support an application that uses stored procedures, or when replicating a single procedure invocation is more efficient than replicating numerous, individual data-changing operations that are produced by a single procedure invocation.

Mirror Replication Agent provides the following features to allow you to select replicated transactions and procedures: