SDE Feature Class Update Problems to Microsoft SQL Server Management Studio

[ChristopherPounds]

I have a Versioned SDE Point Feature Class that is going to be accessed through Microsoft SQL Server Management Studio to extract the data to update another SQL Database.  When IT did the initial test extraction everything worked fine.  I have been updating my feature class and when the new data is looked at in the SQL Server the updates that I have made is not in the SQL Database.  I did the edits in my version of the feature class and reconciled and posted the data back to the default version.  The changes can be seen in the default version in ArcMAP, but when that database is viewed in SQL it cannot be seen.  So my question is does anybody know what is going on or how to fix this problem?  I am new ArcSDE and SQL so my knowledge of what might be going wrong is limited, so hopefully someone can help me out.

Thanks

[JakeSkinner]

When editing a versioned feature class, the edits are stored in the delta (A & D) tables.  The edits will not be moved to the base table until you perform a compress. 

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//002q0000007v000000.htm

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00270000001v000000.htm

When you register a feature class as versioned, you have the option to 'Move Edits to Base'.  If this option is checked, the edits are automatically moved to the base table once the edits are saved.  However, you must be editing the SDE.Default version.  This option will not work for child versions.

[JamesFieman]

Six years after, this helped me solve the same issue. Thank you so much Jake!!

[ChristopherPounds]

Thanks for the Tips.

I have talked with our IT department and a compress is run every night and there is a message that says the compress is always run successfully.  But after looking into it more the changes that have been made are not being updated on the SQL.  The add and delete tables are still there and not being brought over.  Tonight they are going to run an analyze along with the compress, as well as making sure all versions besides the default are deleted before they are run.

[JakeSkinner]

Here is a great article that provides steps on compressing a database to state 0:

http://resources.arcgis.com/content/kbase?fa=articleShow&d=29160

[ChristopherPounds]

Thanks.  I think the problems we are having are with not properly deleting versions.  Hopefully after the compress runs tonight everything will be working.