Multiplex servers and remote data access [CR 426772]

This section was omitted from the Sybase IQ System Administration Guide. It should appear after the section “Using remote procedure calls (RPCs)” in Chapter 16, “Accessing Remote Data”.

Sybase IQ supports remote data access among servers in a multiplex configuration in all directions:

• Write server to query server

• Query server to write server

• Query server to query server

For example, the write server may be defined as a remote server to a query server and proxy tables may be defined on the query server for tables on the write server.

Consider the following when using remote data access among multiplex servers:

• Use server class ASAODBC or ASAJDBC for IQ servers

• Use proxy table names that differ from local table names to avoid multiplex static collisions. For example, if a query server local store has a table named employee, then the proxy table name should not be employee.

• Add remote definitions created on the query servers to the sp_mpxcfg_<servername> stored procedure so that they persist after a multiplex SYNCHRONIZE. If you do not add the definitions to the sp_iqmpxcfg_<servername> procedure, they disappear after SYNCHRONIZE.

  For more information on the sp_mpxcfg_<servername> procedure, please see “Synchronizing query servers” in Chapter 5, “Working with Database Objects” in the Sybase IQ System Administration Guide and

• A remote server definition that points to the current server returns an expected server definition is circular error if attempting to use that remote server definition.