Monthly Archives: March 2015
In a versioned environment, all edits are stored in what we call delta tables, or Adds and Deletes tables, and these tables are assigned to a unique state ID. Edits are held in the delta tables to handle any conflicts in a multi-user enterprise geodatabase. A compress operation trims the delta tables of any unreferenced state ids, consolidating the states lineage down to one state. If a state is still being referenced, it will remain in the delta tables, resulting in a partial compress.
In a fully compressed geodatabase, there are no rows in the delta tables, and the state tree is trimmed back to one state, state_id=0. Although a full compress is ideal, it is not always necessary and in some cases may not even be practical. For example, if there are many multi-generation replicas in your geodatabase that are not unregistered before the compress, you will need to send changes for all of these replicas to achieve a full compress. If there are many Two-way replicas, and you intend to fully compress both the parent and the child geodatabases, this process of synchronization will need to be done separately from both geodatabases, even if there are no changes to be sent.
This blog post provides updated deprecation information regarding ArcGIS 10.3 and 10.2.x. The first version of the 10.3 series was released in December 2014. Starting in 2014, with the release of ArcGIS 10.2.1, the pattern for the deprecation plan changed from a … Continue reading
The Esri Support Services team will be at the 2015 Esri Developer Summit, and we will be offering appointments for your technical questions. Specialists in all areas of Esri software will be available to assist with your questions. Users attending the … Continue reading