Available with Standard or Advanced license.
As a versioned geodatabase is edited over time, delta tables increase in size and the number of states increases. The larger the tables and the more states, the more data ArcGIS must process every time you display or query a version. The greatest impact on performance, therefore, is not the number of versions but the amount of change contained in the delta tables for each version. As a result, versions can have different query response times.
To maintain database performance, the geodatabase administrator must periodically run the Compress command to remove unused data and states. Only the geodatabase administrator can run a compression operation. Compressing performs two key tasks:
- It removes unreferenced states and their associated delta table rows.
- It moves entries in the delta tables common to all versions into the base tables, reducing the amount of data the database needs to search through for each version query, thereby improving query performance and system response time.
When a large volume of uncompressed changes has accumulated, compressing the database can take hours. To avoid this, compress on a regular basis. It is a good idea to compress at the end of every day or after a period of high database activity such as data loading.
During a compression operation, users can stay connected to the geodatabase. If any user is editing a version, the branch for that state is locked and will not take part in the compression. It's best, therefore, to have all users disconnect before starting to ensure the entire state tree can be compressed.
If you ever need to stop a compression operation before it completes, you can end it at any time. This will not leave the database in an inconsistent state. You can continue compressing at a later time.
It is important to update statistics for every versioned feature class and table in the geodatabase after compressing. After edits and a database compression have taken place, database statistics are no longer accurate. This hurts query performance. Individual data owners can update the statistics on their feature classes and tables using the Analyze Datasets geoprocessing tool.