How to Compress geodatabase

[tongkimongki]

dear experts,

I tried to compress my geodatabase but i dont know wether it has been compressed or not. i have checked using

sdeversion -o describe -V DEFAULT -i 5151 -u sde -p sde it shows that STATE ID is 144.
I have also followed this article "http://resources.arcgis.com/content/kbase?fa=articleShow&d=29160".

Here is what i did :

1. Create new feature class
2. Register As Versioned
3. Do some editings on default version and save
4. Compress the geodatabase using catalog or compress using "sdeversion -o compress -N -u sde -p sde -i 5151 -s SERVER1 -D GDB"

I only have SDE as user and i edited the feature class using sde account.
After the compress, the base table is still empty. All edits are still in the A table. All data from A table are moved to base table if I do Unregister As Versioned.

From "http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_dotnet_help/index.html#//00290000005v..." it says that : The compress operation removes the states that are no longer referenced by a version and CAN MOVE ROWS IN THE DELTA TABLES TO THE BUSINESS TABLE.


Did i do something wrong ? What is the compress actually doing ? Can you give me an example ? I expect that after compress all data from A table will be moved to base table...

My environment : Arcgis 9.3.1, Arcsde 9.3.1, Oracle 10gR2, OS: Vista Business.

Thanks.

[VishalPahuja]

You can see if the compress finished successfully or not in the compress_log table in the sde schema. It will also tell you how many states was it able to compress.

Getting all the edits from the delta tables to the base table depends of how your state tree looks. If you are seeing that your default is pointing to state 44, there might be some other versions or something else (replicas, synch versions and so on) are pinning the state tree and preventing flushing of the edits from the delta table to the base table.


What are the contents of the versions table in the sde schema?

[CherylCleghorn]

Your versioned editing workflow will dictate the extent to which the edits would be moved to the business table. For example a) if you have replicas then SDE uses some system versions for replication purposes b) if you have versions which cannot be reconciled/posted at this time they may be pinning the state tree as mentioned by Vishal. I would suggest that you contact Technical Support so that they can look at your versioning workflow and provide information on whether or not you will be able to compress the edits to state 0. Note that compress to state 0 is not a necessity. Based on your end goal, Technical Support may also be able to provide you alternative workflows.