Multiplex Administration with Interactive SQL

If you prefer the flexibility of scripts or are familiar with Interactive SQL from other products, use Interactive SQL.

Interactive SQL is a command line interface that lets you enter SQL statements individually or run them in command scripts to query, modify, or load Sybase servers, including Sybase IQ.

• Starting Multiplex Servers from the Command Line
  To start and stop IQ multiplex servers interactively, use Sybase Central or the start server utility, start_iq. To start IQ multiplex servers in scripts, you may use command line parameters.
• Checking Server Status in Interactive SQL
  Check the server status to determine if any servers are not responding or not included in the multiplex, and to see which server will be the new coordinator in the event of a failover.
• Adding Multiplex Servers with Interactive SQL
  Follow these steps to add multiplex servers from Interactive SQL.
• Renaming Multiplex Servers with Interactive SQL
  You can use Interactive SQL to change the name of a multiplex server.
• Requirements for Altering Multiplex Servers
  Familiarize yourself with requirements and results before you alter a multiplex server.
• Changing the Database File Path with Interactive SQL
  If you have to move your database, for example to a disk with more space, you can change the file path with Interactive SQL.
• Changing Server Roles with Interactive SQL
  You can use Interactive SQL to change a reader to a write server.
• Changing Host and Port with Interactive SQL
  You can use Interactive SQL to change the host and port information for a multiplex server.
• Including or Excluding Servers with Interactive SQL
  If a multiplex secondary server will be shut down for an extended period of time, exclude that server from the multiplex.
• Designating Failover Node with Interactive SQL
  You must designate a failover node to continue the coordinator role in the event that the current coordinator is unable to continue.
• Requirements for Dropping Multiplex Servers
  Familiarize yourself with requirements and results before you drop a multiplex server.
• Dropping Multiplex Servers with Interactive SQL
  Dropping a secondary server removes it from the multiplex configuration.
• Synchronizing Servers from the Command Line
  Synchronizing copies the coordinator's version of the database catalog to secondary servers.
• Counting User Connections
  To avoid exceeding the maximum number of connections, periodically check the current number of user connections.