SQL Remote User's Guide
  Setting Up SQL Remote
    Preparing your Adaptive Server Enterprise server

Command-line installation of the stable queue

The stable queue is a pair of database tables that hold transactions until they are no longer needed by the replication system. Every Adaptive Server Enterprise database participating in a SQL Remote installation needs a stable queue.

For detailed information about the stable queue, see The stable queue.

The stable queue can exist in the same database as the database taking part in SQL Remote, or in a separate 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.

To install the stable queue

1. Locate the stable queue initialization script stableq.sql in your SQL Remote installation directory.

2. Make a backup copy of the stableq.sql script file. Then add the following two lines to the beginning of stableq.sql:

   use database_name
   go

   where database_name is the name of the database that will hold the stable queue.

   These two lines set the current database to database_name, so that the stable queue is created in the database_name database. The stable queue tables are owned by the database owner.

3. Run the script against your Adaptive Server Enterprise server.

   Change to the directory holding the stable queue script, and enter the following command line (which should be entered all on one line) to run the script:

   isql -S server-name -U login_id -P password -i STABLEQ.SQL -o logfile

   where server-name is the name of the Adaptive Server Enterprise, login_id and password correspond to a user with system administrator permissions on the server who owns the database, and logfile is the name of a log file to hold the log information from the script.

   The login_id must correspond to the name used by the Message Agent. For more information, see The Message Agent and replication security.

4. Inspect the log file to confirm that the tables and procedures were created without error.