topic SDE Compression and named versions in Data Management Questions https://community.esri.com/t5/data-management-questions/sde-compression-and-named-versions/m-p/736825#M41638 <HTML><HEAD></HEAD><BODY><P>There is much discussion about compression and I am hoping someone can clear up an issue I am having. We are using versioned editing. Each user has a version that they have created under their own connections. We were having an issue with compression ending states being high - around 40. Many of the versions were old and some were stale. So I rec/posted and deleted the versions. end state was 1. Then I asked everyone to create a new version for themselves.</P><P></P><P>The problem with this is that not everyone used the same name in creating their new version so many of the datasources in their maps became broken. It was a hassle, but the performance gains of the near-full compression were notable and worth the trouble. However, now that users have recreated their versions my state count is going up again after compression. Even if I reconcile the versions first, I can't get below 10 ending states - we have 10 versions.</P><P></P><P>I would like to script the deletion and recreation of the versions as part of an automated workflow, but since the users own their versions, I would have to have a connection as each user to be able to do that. Is that correct? I have the same issue with rebuilding indexes and analyzing datasets...I need to do it under the data owner connection - is that correct?</P><P></P><P>Should I just force all versions to be owned by DBO? Am I missing something that will allow me to achieve what I want without users having to constantly recreate their own versions? Is it normal that each version will account for at least 1 end state after compression even if it is first reconciled?</P></BODY></HTML> Wed, 02 Sep 2015 20:03:10 GMT collindegueurce 2015-09-02T20:03:10Z SDE Compression and named versions https://community.esri.com/t5/data-management-questions/sde-compression-and-named-versions/m-p/736825#M41638 <HTML><HEAD></HEAD><BODY><P>There is much discussion about compression and I am hoping someone can clear up an issue I am having. We are using versioned editing. Each user has a version that they have created under their own connections. We were having an issue with compression ending states being high - around 40. Many of the versions were old and some were stale. So I rec/posted and deleted the versions. end state was 1. Then I asked everyone to create a new version for themselves.</P><P></P><P>The problem with this is that not everyone used the same name in creating their new version so many of the datasources in their maps became broken. It was a hassle, but the performance gains of the near-full compression were notable and worth the trouble. However, now that users have recreated their versions my state count is going up again after compression. Even if I reconcile the versions first, I can't get below 10 ending states - we have 10 versions.</P><P></P><P>I would like to script the deletion and recreation of the versions as part of an automated workflow, but since the users own their versions, I would have to have a connection as each user to be able to do that. Is that correct? I have the same issue with rebuilding indexes and analyzing datasets...I need to do it under the data owner connection - is that correct?</P><P></P><P>Should I just force all versions to be owned by DBO? Am I missing something that will allow me to achieve what I want without users having to constantly recreate their own versions? Is it normal that each version will account for at least 1 end state after compression even if it is first reconciled?</P></BODY></HTML> Wed, 02 Sep 2015 20:03:10 GMT https://community.esri.com/t5/data-management-questions/sde-compression-and-named-versions/m-p/736825#M41638 collindegueurce 2015-09-02T20:03:10Z