Limitations creating proxy tables

To take advantage of the complete feature set of Component Integration Services, use isql or SQL Advantage to execute command line arguments.

The limits for creating proxy tables are:

If a proxy table is based on an existing table or view and you want to create multiple tables in a single batch, you cannot change any column definitions.
You can specify the name for the proxy tables. To create a single table at a time, you must have fewer columns in the proxy table than the original.
Column datatypes need not be identical, but they must be convertible in both directions, or a column datatype mismatch error occurs, and the command is aborted.
If you are creating a proxy table based on an RPC, base the table definition on the result set that you expect from the RPC.
The Adaptive Server Plugin allows you to create proxy tables for the following non-Adaptive Server datasources:
- Adaptive Server Anywhere
- Oracle
- Adaptive Server IQ
- DB2
- MicroSoft SQLServer
If you are creating a proxy table and remote table at the same time, you have full options for creating the proxy table. The remote table is created using the definitions for the proxy table or their equivalents on heterogeneous servers.
If a column name in a remote table or view is an Adaptive Server keyword or contains an illegal character, creation of the proxy table fails. To work around this problem, create the proxy table using isql or SQL Advantage and use the set quoted identifier parameter because the ASE plug-in doesn’t support quoted identifier.