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:
If the table already exists at the remote storage location, use the CREATE EXISTING TABLE statement. This statement defines the proxy table for an existing table on the remote server.
If the table does not exist at the remote storage location, use the CREATE TABLE statement. This statement creates a new table on the remote server, and also defines the proxy table for that table.
You cannot modify data in a proxy table when you are within a savepoint. See Savepoints within transactions.
When a trigger is fired on a proxy table, the permissions used are those of the user who caused the trigger to fire, not those of the proxy table owner.
Specify proxy table locations
Create proxy tables (Sybase Central)
Create proxy tables with the CREATE EXISTING TABLE statement
Create a proxy table with the CREATE TABLE statement
List the columns on a remote table
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|