Stable Queues

When you install Replication Server, you set up a disk partition that Replication Server uses to establish stable queues. During replication operations, Replication Server temporarily stores updates in these queues.

There are three types of stable queues, each of which stores a different type of data:

Inbound queue – holds messages only from a Replication Agent. If the database you add contains primary data, or if request stored procedures are to be executed in the database for asynchronous delivery, Replication Server creates an inbound queue and prepares to accept messages from a Replication Agent for the database.
Outbound queue – holds messages for a replicate database or a replicate Replication Server. There is one outbound queue for each of these destinations:
- For each replicate database managed by a Replication Server, there is a Data Server Interface (DSI) outbound queue.
- For every Replication Server to which a Replication Server has a route, there is a Replication Server Interface (RSI) outbound queue.
Subscription materialization queue – holds messages related to newly created or dropped subscriptions. This queue stores a valid transactional “snapshot” from the primary database during subscription materialization or from a replicate database during dematerialization.

You can add more partitions later if your replication system requires more space for stable queues.

See the Replication Server Troubleshooting Guide for information on how to examine queue contents for troubleshooting purposes.

Queue Management
Replication Server uses the Stable Queue Manager (SQM) thread to manage each stable queue.
Partitions for Stable Queues
Replication Server stores messages destined for data servers or other sites on partitions.
Use Disk Files for Stable Queues
To use a disk file for a partition, create the file before you execute the create partition command.

Parent topic: Transaction Handling with Replication Server

Related concepts

Partitions for Stable Queues