topic Re: ArcSDE Full Compress - Results in Corrupted Feature Classes in Data Management Questions https://community.esri.com/t5/data-management-questions/arcsde-full-compress-results-in-corrupted-feature/m-p/259340#M14812 <HTML><HEAD></HEAD><BODY><SPAN>I have come across the same issue. If anyone has any insight we would be grateful. </SPAN><BR /><BR /><SPAN>James </SPAN><BR /><BR /><BLOCKQUOTE class="jive-quote">We are running ArcGIS 9.3.1.&nbsp; We perform an ArcSDE compress on a 3-4 week basis.&nbsp; <BR /><BR />We satisfy all the conditions to achieve a Full Compress.&nbsp; <BR /><BR />We have encountered corrupted (versioned) feature classes as a result of a full compress on a <BR /><BR />number of occasions.&nbsp; The Business, F and S tables become out of sync, and hence the fc cannot <BR /><BR />be manipulated, viewed, deleted, etc.&nbsp; I have managed to reconstruct this relationship using&nbsp; <BR /><BR />DBMS tools, but this kind of practice is not sustainable and is big waste of time.&nbsp; <BR /><BR />A full compress was meant to be a good thing.&nbsp; The catch 22 for us is our organisation edits <BR /><BR />heavily in arcSDE with a number of editors and if we put off a 'full' compress for too long the <BR /><BR />performance of the database slows terribily. (ie hundreds of thousands of records in the delta <BR /><BR />tables, I understand is bad practice).&nbsp;&nbsp; It seems the pruning done behind the scenes is not going <BR /><BR />according to plan! Has anyone encountered the same issue after a full compress <BR /><BR />is achieved?&nbsp; We are close to upgrading to ArcGIS 10.</BLOCKQUOTE></BODY></HTML> Tue, 09 Aug 2011 12:51:12 GMT JamesSimard1 2011-08-09T12:51:12Z ArcSDE Full Compress - Results in Corrupted Feature Classes https://community.esri.com/t5/data-management-questions/arcsde-full-compress-results-in-corrupted-feature/m-p/259339#M14811 <HTML><HEAD></HEAD><BODY><SPAN>We are running ArcGIS 9.3.1.&nbsp; We perform an ArcSDE compress on a 3-4 week basis.&nbsp; </SPAN><BR /><BR /><SPAN>We satisfy all the conditions to achieve a Full Compress.&nbsp; </SPAN><BR /><BR /><SPAN>We have encountered corrupted (versioned) feature classes as a result of a full compress on a </SPAN><BR /><BR /><SPAN>number of occasions.&nbsp; The Business, F and S tables become out of sync, and hence the fc cannot </SPAN><BR /><BR /><SPAN>be manipulated, viewed, deleted, etc.&nbsp; I have managed to reconstruct this relationship using&nbsp; </SPAN><BR /><BR /><SPAN>DBMS tools, but this kind of practice is not sustainable and is big waste of time.&nbsp; </SPAN><BR /><BR /><SPAN>A full compress was meant to be a good thing.&nbsp; The catch 22 for us is our organisation edits </SPAN><BR /><BR /><SPAN>heavily in arcSDE with a number of editors and if we put off a 'full' compress for too long the </SPAN><BR /><BR /><SPAN>performance of the database slows terribily. (ie hundreds of thousands of records in the delta </SPAN><BR /><BR /><SPAN>tables, I understand is bad practice).&nbsp;&nbsp; It seems the pruning done behind the scenes is not going </SPAN><BR /><BR /><SPAN>according to plan! Has anyone encountered the same issue after a full compress </SPAN><BR /><BR /><SPAN>is achieved?&nbsp; We are close to upgrading to ArcGIS</SPAN><SPAN> 10.</SPAN></BODY></HTML> Thu, 11 Nov 2010 01:01:06 GMT https://community.esri.com/t5/data-management-questions/arcsde-full-compress-results-in-corrupted-feature/m-p/259339#M14811 BillFish 2010-11-11T01:01:06Z Re: ArcSDE Full Compress - Results in Corrupted Feature Classes https://community.esri.com/t5/data-management-questions/arcsde-full-compress-results-in-corrupted-feature/m-p/259340#M14812 <HTML><HEAD></HEAD><BODY><SPAN>I have come across the same issue. If anyone has any insight we would be grateful. </SPAN><BR /><BR /><SPAN>James </SPAN><BR /><BR /><BLOCKQUOTE class="jive-quote">We are running ArcGIS 9.3.1.&nbsp; We perform an ArcSDE compress on a 3-4 week basis.&nbsp; <BR /><BR />We satisfy all the conditions to achieve a Full Compress.&nbsp; <BR /><BR />We have encountered corrupted (versioned) feature classes as a result of a full compress on a <BR /><BR />number of occasions.&nbsp; The Business, F and S tables become out of sync, and hence the fc cannot <BR /><BR />be manipulated, viewed, deleted, etc.&nbsp; I have managed to reconstruct this relationship using&nbsp; <BR /><BR />DBMS tools, but this kind of practice is not sustainable and is big waste of time.&nbsp; <BR /><BR />A full compress was meant to be a good thing.&nbsp; The catch 22 for us is our organisation edits <BR /><BR />heavily in arcSDE with a number of editors and if we put off a 'full' compress for too long the <BR /><BR />performance of the database slows terribily. (ie hundreds of thousands of records in the delta <BR /><BR />tables, I understand is bad practice).&nbsp;&nbsp; It seems the pruning done behind the scenes is not going <BR /><BR />according to plan! Has anyone encountered the same issue after a full compress <BR /><BR />is achieved?&nbsp; We are close to upgrading to ArcGIS 10.</BLOCKQUOTE></BODY></HTML> Tue, 09 Aug 2011 12:51:12 GMT https://community.esri.com/t5/data-management-questions/arcsde-full-compress-results-in-corrupted-feature/m-p/259340#M14812 JamesSimard1 2011-08-09T12:51:12Z