Original User: blin26
Hi Jamal,
First of all, analyse datasets and rebuild indexes will not contribute to the compress process, those however, will improve your overall database performance.
Secondly, only a FULL compress will push all the edits to the business (base) tables. In your Python script, the compress will only be treated as a partial compress, but not a full compress.
From the web help link I provided early, here is the detail information regarding FULL compress.
"Fully compressing a geodatabase
In a fully compressed geodatabase, there are no rows in the delta tables and the state tree is trimmed back to zero. Performance improvement is greatest if the geodatabase is fully compressed. To achieve this, do the following:
�?�Reconcile and post all outstanding changes in child versions to the DEFAULT version. As the geodatabase administrator, you can see in what order versions should be reconciled by default by opening the Reconcile Order subtab of the Versions tab on the Geodatabase Administration dialog box. See Version properties for information on the Reconcile Order subtab.
�?�Delete the versions themselves after you have reconciled and posted edits.
�?�Make sure no user is connected.
�?�Perform the compression operation."
You then can recreate the user versions after the full compress.
Thanks,
Ben L.