Compression to SQL problems

[Anonymous User]

Having issues with .sde compression showing up in the SQL tables.  The project spanned 20 weeks.  Each week new data was added and compressed in ArcMap.  Weeks 1-17 appeared in SQL immediately upon compression.  Weeks 18-20 have yet to show up.  I am at a loss as to what exactly has happened that SQL is no longer receiving the .sde compression updates.  Advice/Ideas?

[KenGalliher1]

Are you compressing all the way to "State 0"?  Sometimes existing connections or orphaned states can prevent edits from moving to the base tables.

Are you still having this issue?

[RussellBrennan]

CEI_gis,

Individual edits will appear in the base table in three situations:
- when the edits are common to all versions (reconciled and posted between all versions) and a compress is executed.
- if you are using the option to 'move edits to base' when you register your data as versioned and you save your edits in the Default version.
- you use non-versioned editing.

My best guess based on your description is that you have edits that are not showing up in all of your versions. This is normal for most geodatabases, unless you are attempting to edit your tables directly with SQL there is likely nothing to worry about.

Versioning:
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00270000000r000000.htm

Here is some doc on deciding how to register as versioned:
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Deciding_how_to_register_data/00270000...

Compress doc:
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00290000005v000000.htm

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/The_compress_operation_and_geodatabase...

If you have further questions it is likely best to contact Esri Technical Support and they can give you more info.

Hope this helps,