Remote table mappings

Sybase IQ presents tables to a client application as if all the data in the tables were stored in the database to which the application is connected. Internally, when Sybase IQ executes a query involving remote tables, it determines the storage location and accesses the remote location to retrieve data.

To have remote tables appear as local tables to the client, you create local proxy tables that map to the remote data.

StepsCreating a proxy table

  1. Define the server where the remote data is located. This specifies the type of server and location of the remote server. For more information, see “Working with remote servers”.

  2. Map the local user login information to the remote server user login information if the logins on the two servers are different. For more information, see “Working with external logins”.

  3. Create the proxy table definition. This specifies the mapping of a local proxy table to the remote table. This includes the server where the remote table is located, and the database name, owner name, table name, and column names of the remote table. For more information, see “Working with proxy tables”.

Administering remote table mappings

You can manage remote table mappings and remote server definitions with the Sybase Central GUI or execute SQL statements directly with Interactive SQL.