The diagram in Figure 1-4 shows how the ASE Replicator components work together to replicate transaction operations from a primary database to a replicate database.
The process is slightly different for stored procedure
replication.
Figure 1-4: ASE Replicator transaction replication
The Publisher component reads the primary database’s native Adaptive Server transaction log and builds transaction metadata and operation records that describe the primary transaction.
The Publisher component writes the transaction metadata in the transaction log table and the transaction operation data in the shadow table (or tables) in the Distribution Database.
The Distributor component reads the metadata in the transaction log table, determines the transaction to be applied to a replicate object, then executes the distribution procedure associated with the replicate object.
Distribution procedures read the transaction operation data in the shadow tables, then apply the replicated transaction operations to the CIS proxy tables in the Distribution Database.
CIS propagates the replicated transaction operations in the proxy tables to the replicate tables in the replicate database.
In stored procedure replication, the distribution procedures issue remote procedure calls (RPCs) to the replicate database, instead of applying operations to a CIS proxy table.
