|
|
|
 |
Scalable Geodatabase FunctionalityGeodatabases that utilize ArcSDE technology have additional functionality not available with File geodatabases. These include Multiuser Editing Environment OptionsThere are three options for editing in a scalable geodatabase: Versioned Editing Transactions are packages of work that make changes to databases. GIS databases, like other database applications, must support update transactions that enforce data integrity and application behavior. However, GIS users have specialized transactional requirements, the most important of which is that transactions must span long periods of time (days and months, not just seconds). Versioning is the mechanism that enables the geodatabase to manage and maintain multiple states while preserving integrity in the database. Versioning explicitly records states (versions) of individual features and objects as they are modified, added, and/or "retired." It is the basis for multiple users accessing and editing data simultaneously as well as long transaction support. Simple queries are used to view (and work with) any desired state for a particular point in time or to see a particular user's current version containing his/her edits.
Refer to the following versioning white papers for more information.
Versioned Editing with the Option to Move Edits to Base Registering data as versioned with the option to move edits to base conceptually combines versioned editing with nonversioned editing—with some limitations. This enables versioned editing on the data, but when you're editing the default version, you are making direct changes to the Base tables. There are some restrictions with this editing option. These restrictions include
Nonversioned Editing Editing nonversioned data stored in a scalable geodatabase is equivalent to performing standard database transactions. Users perform a transaction within the scope of an ArcMap edit session. They start the edit session and perform the required operations such as adding, deleting, moving features, and updating attributes. When finished, users save, which commits the changes to the geodatabase as a single "short" transaction. Edits are immediately applied to the Base tables. Replication
Since the replication model is implemented at the scalable geodatabase level, the RDBMSs involved can differ. Geodatabase replication can be used in connected and disconnected environments. It can also work with local geodatabase connections as well as geodataserver objects (through ArcGIS Server), which enable access to a geodatabase over the Internet. Archiving
Geodatabase archiving introduces a historical version. A historical version represents the database as it was at a moment in time and provides a read-only view of the geodatabase for a particular given moment. You can connect to a historical version based on a predefined historical marker or a specified moment in time that you pick from a calendar. A historical marker is a named moment in time that you can create. |
| Home | Products | Services | Industries | Training | Support | Events | News | About ESRI |
Geodatabase replication is a data distribution method provided through ArcGIS. With geodatabase replication, data is distributed across two or more geodatabases so that data changes can be synchronized. It is built on top of the versioning environment and supports the full geodatabase data model including topologies and geometric networks. In this asynchronous model, the replication is loosely coupled, meaning that each replicated geodatabase can work independently and still synchronize changes with one another.
Within a scalable geodatabase, data can be enabled for archiving in a framework that provides the mechanism to capture all data changes in the default version of the geodatabase by preserving the transactional history as an additional archive class. ArcGIS applies transaction time when changes are saved or posted to the default version to record the moment of change to the database.