idea Documentation for ArcSDE database compression needs to include synchronization in both directions more prominently in Data Management Ideas https://community.esri.com/t5/data-management-ideas/documentation-for-arcsde-database-compression/idi-p/934107 <P>More and more GIS Administrators seem to be using non-ESRI applications to access web services via ArcSDE.&nbsp; In order to use non-ESRI apps a full database compression to state_ID=0 must occur.&nbsp; At version 10 and 10.1, in order to get a full compress, it is sometimes necessary to synchronize changes not only from child two-way to parent, but also from parent (SDE.DEFAULT) to child two-way.&nbsp; This step is necessary to clean up the SDE.VERSIONS table which allows for a full compress to state_ID=0.&nbsp;<BR />I spent weeks on this problem, in addition to ESRI Technical Support.&nbsp; THe documentation for this step is only referenced in the ESRI white paper on compression, and only as a special side-note in that documentation.&nbsp; It seems that everywhere else I searched, in addition to the forums, the widely accepted and documented steps to achieve full compress was to<BR />1.) reconcile/post<BR />2.) delete versions<BR />3.) synchronize changes for all replicas from child to parent<BR />4.) compress database, check state_ID.<BR /><BR />However, at version 10 and 10.1 the steps are actually:<BR />1.) reconcile/post<BR />2.) delete versions<BR />3.) synchronize changes for all replicas from child to parent<BR />4.) synchronize changes from parent back to each child two-way replica (even if there are no changes)<BR />5.) compress database, check state_ID.</P><!-- content transformation source ID: 087E00000004YOi --> Fri, 09 Sep 2022 21:49:09 GMT MattSimmons 2022-09-09T21:49:09Z Documentation for ArcSDE database compression needs to include synchronization in both directions more prominently https://community.esri.com/t5/data-management-ideas/documentation-for-arcsde-database-compression/idi-p/934107 <P>More and more GIS Administrators seem to be using non-ESRI applications to access web services via ArcSDE.&nbsp; In order to use non-ESRI apps a full database compression to state_ID=0 must occur.&nbsp; At version 10 and 10.1, in order to get a full compress, it is sometimes necessary to synchronize changes not only from child two-way to parent, but also from parent (SDE.DEFAULT) to child two-way.&nbsp; This step is necessary to clean up the SDE.VERSIONS table which allows for a full compress to state_ID=0.&nbsp;<BR />I spent weeks on this problem, in addition to ESRI Technical Support.&nbsp; THe documentation for this step is only referenced in the ESRI white paper on compression, and only as a special side-note in that documentation.&nbsp; It seems that everywhere else I searched, in addition to the forums, the widely accepted and documented steps to achieve full compress was to<BR />1.) reconcile/post<BR />2.) delete versions<BR />3.) synchronize changes for all replicas from child to parent<BR />4.) compress database, check state_ID.<BR /><BR />However, at version 10 and 10.1 the steps are actually:<BR />1.) reconcile/post<BR />2.) delete versions<BR />3.) synchronize changes for all replicas from child to parent<BR />4.) synchronize changes from parent back to each child two-way replica (even if there are no changes)<BR />5.) compress database, check state_ID.</P><!-- content transformation source ID: 087E00000004YOi --> Fri, 09 Sep 2022 21:49:09 GMT https://community.esri.com/t5/data-management-ideas/documentation-for-arcsde-database-compression/idi-p/934107 MattSimmons 2022-09-09T21:49:09Z Re: Documentation for ArcSDE database compression needs to include synchronization in both directions more prominently https://community.esri.com/t5/data-management-ideas/documentation-for-arcsde-database-compression/idc-p/934108#M819 <HTML><HEAD></HEAD><BODY><P>Here are some resources for getting a complete compress:</P><P></P><P><A href="https://blogs.esri.com/esri/supportcenter/2015/03/24/tips-for-compressing-with-existing-geodatabase-replicas/" title="https://blogs.esri.com/esri/supportcenter/2015/03/24/tips-for-compressing-with-existing-geodatabase-replicas/">Acheiving Full Compress on Geodatabases with Existing Replicas | Support Services Blog</A> </P><P></P><P><A href="http://downloads.esri.com/support/whitepapers/ao_/J9842_GDB_Compress_With_Replicas.pdf" title="http://downloads.esri.com/support/whitepapers/ao_/J9842_GDB_Compress_With_Replicas.pdf">http://downloads.esri.com/support/whitepapers/ao_/J9842_GDB_Compress_With_Replicas.pdf</A> </P></BODY></HTML> Thu, 16 Jun 2016 13:30:50 GMT https://community.esri.com/t5/data-management-ideas/documentation-for-arcsde-database-compression/idc-p/934108#M819 George_Thompson 2016-06-16T13:30:50Z