Contents Index Scanning the transaction log Message Agent operation phases

SQL Remote User's Guide
  Administering SQL Remote for Adaptive Server Enterprise
    How the Message Agent for Adaptive Server Enterprise works

The stable queue


The Message Agent for Adaptive Server Enterprise uses a stable queue to hold transactions until they can be deleted. A stable queue is a pair of database tables that hold messages that may still be needed by the replication system.

SQL Remote for Adaptive Server Anywhere does not use a stable queue.

Stable queue not identical to Replication Server stable queue 
Sybase Replication Server also uses stable queues as storage areas for replication messages. The Replication Server and SQL Remote stable queues perform similar functions, but are not the same thing.
Stable queue location 

The stable queue may be kept in the same database as the tables being replicated, or in a different database. Keeping the stable queue in a separate database complicates the backup and recovery plan, but can improve performance by putting the stable queue workload on separate devices and/or a separate Adaptive Server Enterprise server.

Do not modify the stable queue directly 
The stable queue is maintained by and for the Message Agent. You should not modify the stable queue directly.

The stable queue consists of a set of tables that contain information on all transactions scanned from the transaction log,

For a description of each of the columns of these tables, see Stable Queue tables.


Contents Index Scanning the transaction log Message Agent operation phases