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.
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”.
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”.
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”.
To manage remote table mappings and remote server definitions, you can use Sybase Central or you can use a tool such as Interactive SQL and execute the SQL statements directly.
Creating a proxy table