SAP Sybase IQ remote data access gives you access
to data in other data sources. You can use this feature to migrate data into a
SQL Anywhere database or query data across
databases.
Characteristics of Sybase Open Client and jConnect connections
When SAP Sybase IQ is serving applications over TDS, it automatically sets relevant database options to values compatible with Adaptive Server Enterprise default behavior. These options are set temporarily, for the duration of the connection only. The client application can override them at any time.
Remote Servers
Before remote objects can be mapped to a local proxy table, define the remote server where the remote object is located.
External Logins
SAP Sybase IQ uses the names and passwords of its clients when it connects to a remote server on behalf of those clients. However, this behavior can be overridden by creating external logins.
Proxy tables
Location transparency of remote data is enabled by creating a local proxy table that maps to the remote object. You can use a proxy table to access any object (including tables, views, and materialized views) that the remote database exports as a candidate for a proxy table. Use one of the following statements to create a proxy table:
Joins between remote tables
The following figure illustrates proxy tables on a local database server that are mapped to the remote tables Employees and Departments of the SAP Sybase IQ sample database on the remote server RemoteSA.
Joins between tables from multiple local databases
A SAP Sybase IQ server may have several local databases running at one time. By defining tables in other local SAP Sybase IQ databases as remote tables, you can perform cross-database joins.
Native statements and remote servers
Use the FORWARD TO statement to send one or more statements to the remote server in its native syntax. This statement can be used in two ways:
Remote Procedure Calls (RPCs)
SAP Sybase IQ users can issue procedure calls to remote servers that support the feature.