About compressing a geodatabase |
|
Release 9.3 |
NOTE: It is important not to wait too long between compress operations; the greater the amount of editing activity that takes place, the longer it will take to compress the geodatabase. If you don't compress the geodatabase at least once a week, the compress could take several hours to complete when you do finally run it.
After compressing a geodatabaseYou should update the statistics on your geodatabase after you have run a compress operation. For information on updating statistics, see About updating geodatabase statistics.NOTE: This storage parameter doesn't exist under the DEFAULTS configuration keyword until you add it. If this parameter is not set, the next available online rollback segment will be used. If the rollback segment is not large enough, the compress operation will fail since the transaction will be forced to roll back.
Oracle recommends that you use automatic undo management. Starting with Oracle9i, automatic undo management is done by allocating space in the form of an undo table space instead of allocating rollback segments of different sizes. TipNOTE: Applies to geodatabases created with an ArcGIS Server Enterprise license only
You need to rebuild your business tables’ clustered indexes after running a full compress, because business table fragmentation can occur with a full compress. For information on compressing ArcSDE geodatabases for SQL Server Express, see Compressing a geodatabase on an ArcSDE database server.