Home    |    Concepts   |   API   |   Samples
Concepts > Versioning
SQL Access Using Multiversioned Views

ArcSDE provides SQL access to versioned databases, which is implemented through database views, stored procedures or functions, and triggers on the underlying versioned table schema. The internal details for these views, stored procedures, and triggers vary across databases, but the same general access model is provided for application developers. Taken together, these views, stored procedures, and triggers implement what are referred to as multiversioned views.

SQL access to tables in a versioned database can be enabled on individual tables by creating a multiversioned view on each table using the sdetable command (consult the ArcSDE Administration Command Reference for sdetable syntax) or using Java or C-API.

When a multiversioned view is created, triggers are enabled on the table to allow inserts, updates, and deletes to the columns of the selected version of the table. SQL access to tables on some DBMS releases uses an SQL construct called an INSTEADOF trigger. For more information on multiversioned views, see What are multiversioned views in the ArcGIS Desktop or ArcGIS Server help.

At this release, SQL read access and attribute editing to multiversioned tables is supported on all supported databases except DB2 release 9.5.

See also

Creating a Multiversioned View
Using Multiversioned Views
Executing Queries, Inserts, Deletes, and Updates

When creating and using multiversioned views and executing queries, a version other than DEFAULT should be used.

feedback | privacy | legal