A version is a specific configuration of the versioned database that is not affected by changes in other versions of the database. A version is identified by a unique name (the version name) and is owned by the user who creates it. Creating a new version makes a logical copy of the database specific for the user that created it. There is no duplication of data.

A versioned database will contain a list of available versions. Users identify the desired version of the database by selecting a version from this list. When no version is specified, ArcSDE will look for a version named DEFAULT.
Over time, a version may represent different configurations of the versioned database. For example, a database may contain three versions: WORKING, which represents the working state of the database, and two edit versions: EDIT1 and EDIT2, which are derived from the WORKING version. When the EDIT1 version is saved back to WORKING, the WORKING version will represent a new configuration of the database. The configuration will change again when the EDIT2 version is saved back to WORKING.

Only the owner of a version may remove it from the database. If a version is a parent to one or many dependant versions, then it may not be deleted.

Versions may be private, protected, or public. Private versions are only accessible by the version owner, making the owner the only user who may create a child version. Protected versions can be viewed by other users but only edited by the owner. Public versions are accessible to any user, and allow users other than the owner to create child versions.