ArcSDE provides SQL access to versioned databases, which is implemented through database views, stored procedures, 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 is enabled on individual tables by creating a multiversioned view on each table using the sdetable command. Multiversioned views are used to access attribute columns, not spatial columns. When a multiversioned view is created, triggers are enabled on the table to allow inserts, updates, and deletes to the attribute columns of the selected version of the table. SQL access to tables uses an SQL construct called an INSTEADOF trigger. These triggers are not available on all DBMS releases.

At this release, SQL access to multiversioned tables is supported on the SQL Server 2000 and 2005, Oracle, IBM DB2, and Informix databases. SQL access to multiversioned tables is not supported on SQL Server 7, because this database release does not support INSTEADOF triggers.

Note: Views are read-only for Informix databases, therefore, you cannot use multiversioned views to edit attribute columns in the base table.

SQL read access to versioned data is available to all databases that support any access to multiversioned tables. Oracle and SQL Server 2000 and 2005 allow users to create and delete versions using SQL. Oracle, SQL Server 2000 and 2005, and IBM DB2 allow users to edit attribute columns in multiversioned tables using SQL.

See also

Creating a Multiversioned View

Using Multiversioned Views

Executing Queries, Inserts, Deletes, and Updates

In order to create and use multiversioned views and execute queries, a user named version should be used.