Contents Index Using SQL Remote with Replication Server Architecture for Replication Server/SQL Remote installations

SQL Remote User's Guide
  Using SQL Remote with Replication Server

When you need to use the SQL Remote Open Server


The Message Agent for Adaptive Server Enterprise scans the Adaptive Server Enterprise transaction log to populate the stable queue, as described in the section The stable queue). SQL Remote messages are built from the transactions in the stable queue.

The Message Agent uses the same interface to scan the transaction log as the Replication Agent for Adaptive Server Enterprise. This means the Message Agent cannot scan the transaction log of an Enterprise database that is a primary site in a Replication Server setup (or a replicate site that allows asynchronous updates to primary data).

If there is a Replication Agent running against your Adaptive Server Enterprise database, you must use the SQL Remote Open Server as an additional component. In this case, SQL Remote is set up so that Replication Server populates the stable queue. The SQL Remote Message Agent does not scan the transaction log. Instead, the SQL Remote Open Server receives transactions from Replication Server. The transactions are parsed by the SQL Remote Open Server and stored in the SQL Remote stable queue.

This chapter assumes knowledge of Replication Server. For information, see your Replication Server documentation.

Open Server runtime components required 
The Open Server runtime components are not included with SQL Remote. You must obtain them separately from Sybase in order to use the SQL Remote Open Server.

Contents Index Using SQL Remote with Replication Server Architecture for Replication Server/SQL Remote installations