Compress, Analyze, Rebuild Spatial Index, Default, and Versions

[TimHayes]

I have the DEFAULT (Parent) with two Versions (Children). Each Version is a direct descendent from the Default.

I do not want to run a FULL Compression yet. But, would like to do a "partial" compression (not the FULL Compression where I delete the Versions first).

Questions:

- Should I Compress each Version separately, and also compress Default? OR should I just compress the Default? If I just compress the Default, will it automatically apply to each Version?

- Should I Analyze each Version separately, and also the Default? If I just Analyze the Default, will it automatically apply to each Version?

- Should I Rebuild Spatial Index for each Version separately, and also the Default? If I just Rebuild Spatial Index for the Default, will it automatically apply to each Version?

[JakeSkinner]

Hi Timothy,

1. Should I Compress each Version separately, and also compress Default?  OR should I just compress the Default? If I just compress the Default,  will it automatically apply to each Version?

- A compress operation operates against all states in the geodatabase, regardless of the version you are currently connected to.  If you are using ArcGIS 10.1, you can view the Reconcile Order tab to see which order to reconcile your versions.

2. Should I Analyze each Version separately, and also the Default? If I  just Analyze the Default, will it automatically apply to each Version?

- When working with tables or datasets, an Analyze will update the statistics  of base tables, delta tables, and archive tables, along with the  statistics on those tables' indexes.  Therefore, you will not have to analyze versions separately.  When executing the analyze on a feature class/table, regardless of the version, all tables' indexes mentioned above will be updated.

3.  Should I Rebuild Spatial Index for each Version separately, and also  the Default? If I just Rebuild Spatial Index for the Default, will it  automatically apply to each Version?  

- The spatial index is the same for all versions.  If you made a substantial amount of edits where you added or deleted a large amount of features, you should recalculate your spatial index after you perform the compress.  You should also rebuild RDBMS indexes to help improve the performance, as indexes can become fragmented due to frequent editing and compressing of the data.  See the following article here.

[TimHayes]

Compress, Analyze, and Rebuild Spatial Index only is done on the DEFAULT? No need to do this on Versions which are a Child to DEFAULT? I think this is what you are saying?

[VinceAngelo]

Keep in mind that changes to more than one table can reside in a single state (e.g., feature
dataset edits). Versioning is implemented as a single state tree across all tables in the instance.

Indexes are a property of individual tables.  All the states (edits) associated with a single versioned
table reside in the set of tables (business, adds, and deletes) -- you *can't* index different states
differently.

- V