A proxy table is a locally named alias, displayed as a table, that points to a remote
object such as an entire table, a view, a materialized view, or a set of remote table columns.
Before you can map remote objects to a local proxy table, you must define the remote server
where the remote object is located.
Prerequisites
| Database Version |
Table Privileges |
|---|
| SAP Sybase IQ 15.3 and 15.4 |
Proxy table to be owned by self:- Requires RESOURCE authority with CREATE permission on the main
store dbspace in which the table is created.
Proxy table to be owned by any user – Requires DBA
authority.
|
| SAP Sybase IQ
16.0 |
Proxy table to be owned by self – Requires CREATE PROXY TABLE system
privilege.
Proxy table to be owned by any user – Requires one of: - CREATE ANY TABLE system privilege
- CREATE ANY OBJECT system privilege.
|
-
The
SAP Sybase IQ resource is authenticated and running.
-
In a multiplex configuration, the coordinator node is
running.
-
Before you can map remote objects to a local proxy table, you must define the
remote server where the remote object is located.
Task
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.
Location transparency of remote data is enabled by creating a local proxy table that
maps to the remote object.
- In the Perspective Resources view, select the resource and select .
- In the Administration Console, expand .
- Click the arrow next to Proxy Tables and select
New.
The Create Proxy Table wizard appears.
- On the Server and User page, specify
| Option |
Description |
|---|
| Select a resource for which the proxy table will be created |
From the list, select the resource for which the proxy table will be
created. |
| To which remote server do you want to create the proxy table? |
From the list, select the remote server. |
| Which user will own the proxy table? |
From the list, select the user to own the table. Default is dba
user. |
| (Optional) Remote database name |
Specify the name of the remote database associated with the remote
server. Note: You specify a remote database on which your remote login has
system privileges.
|
- Click Next.
- On the Table Selection page, specify:
| Option |
Description |
|---|
| Which table do you want to use for this proxy table? |
From the list, select the object on the remote server (table / view /
materialized view) that will be used as the target of the local proxy. |
| What do you want to name the new proxy table. |
Enter a unique name for the new proxy table. You cannot create two tables
with the same name under the same user ID. The default name of the proxy table
is the name of the object on the remote server. However, this may not be a
unique name to your user ID. |
- Click Next.
- On the Column Selection page, select the columns to be used in the proxy table.
Default is to use all columns.
- Click Next.
- On the Comments page, add a descriptive comment for the proxy table. Comments help
you organize the database.
- Click Finish.