<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Compressing SDE database in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071440#M43400</link>
    <description>&lt;P&gt;&lt;STRONG&gt;BUG-000136627 &lt;/STRONG&gt;: Diagnose Version Tables and Repair Version Tables fail and return Error 999999 when the sde_tables_locks table has the tables_locks_fk foreign key constraint.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Jun 2021 13:07:57 GMT</pubDate>
    <dc:creator>MichelleThorne</dc:creator>
    <dc:date>2021-06-23T13:07:57Z</dc:date>
    <item>
      <title>Compressing SDE database</title>
      <link>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071404#M43398</link>
      <description>&lt;P&gt;I am working in ArcGIS Desktop, 10.8.1 version, on Windows 10.&amp;nbsp; We discovered recently that when compressing the SDE database we are not compressing to 1.&amp;nbsp; We compress to 2.&lt;/P&gt;&lt;P&gt;We were told it is a bug and weren't sure when, or if this would be corrected but everything works in ArcPro.&lt;/P&gt;&lt;P&gt;Is this true that ArcGIS Desktop, 10.8.1 is unable to compress to 1?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Michelle&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 11:30:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071404#M43398</guid>
      <dc:creator>MichelleThorne</dc:creator>
      <dc:date>2021-06-23T11:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: Compressing SDE database</title>
      <link>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071422#M43399</link>
      <description>&lt;P&gt;I would say compressing to 1 or 2 is a good thing. Is there a specific reason you are trying to get to "1"?&lt;BR /&gt;&lt;BR /&gt;Do you have a bug # for reference?&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 12:44:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071422#M43399</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2021-06-23T12:44:42Z</dc:date>
    </item>
    <item>
      <title>Re: Compressing SDE database</title>
      <link>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071440#M43400</link>
      <description>&lt;P&gt;&lt;STRONG&gt;BUG-000136627 &lt;/STRONG&gt;: Diagnose Version Tables and Repair Version Tables fail and return Error 999999 when the sde_tables_locks table has the tables_locks_fk foreign key constraint.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 13:07:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071440#M43400</guid>
      <dc:creator>MichelleThorne</dc:creator>
      <dc:date>2021-06-23T13:07:57Z</dc:date>
    </item>
    <item>
      <title>Re: Compressing SDE database</title>
      <link>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071445#M43401</link>
      <description>&lt;P&gt;That defect does not impact the compress function. It is also listed as fixed at ArcGIS Pro 2.8.x&lt;BR /&gt;&lt;BR /&gt;Are you having any performance issues after the compress to "2"?&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 13:11:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071445#M43401</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2021-06-23T13:11:17Z</dc:date>
    </item>
    <item>
      <title>Re: Compressing SDE database</title>
      <link>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071449#M43402</link>
      <description>&lt;P&gt;No issues I am aware of.&amp;nbsp; We just spent months with ESRI technician trying to get to 1.&amp;nbsp; It seemed important to the technician and the result was a somewhat work around, that may or may not always work, and that it is a bug, that may or may not get fixed by ESRI.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The solution the tech gave, just seemed a bit vague, and we wondered it others were having issues, too. And how important is it to compress to 1?&lt;/P&gt;&lt;P&gt;We do not work in ArcGISPro.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 13:20:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071449#M43402</guid>
      <dc:creator>MichelleThorne</dc:creator>
      <dc:date>2021-06-23T13:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: Compressing SDE database</title>
      <link>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071463#M43404</link>
      <description>&lt;P&gt;Getting to state "0" is a good thing, but not necessary. As long as the compress is successful and there not performance issues after, then state "2" is fine.&lt;BR /&gt;&lt;BR /&gt;Here is a great article that talks about getting a full compress when the EGDB has replicas:&amp;nbsp;&lt;A href="https://community.esri.com/t5/esri-technical-support-blog/tips-for-compressing-with-existing-geodatabase-replicas/ba-p/898380" target="_blank" rel="noopener"&gt;https://community.esri.com/t5/esri-technical-support-blog/tips-for-compressing-with-existing-geodatabase-replicas/ba-p/898380&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I also know that you do not work in Pro, but I would start to look at migrating to using it.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 13:42:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071463#M43404</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2021-06-23T13:42:06Z</dc:date>
    </item>
    <item>
      <title>Re: Compressing SDE database</title>
      <link>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071465#M43405</link>
      <description>&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 13:45:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1071465#M43405</guid>
      <dc:creator>MichelleThorne</dc:creator>
      <dc:date>2021-06-23T13:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: Compressing SDE database</title>
      <link>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1147679#M43861</link>
      <description>&lt;P&gt;Commenting to let folks know: This bug report is intended to address the issue in ArcGIS Pro, but it worked for me on ArcGIS Desktop 10.8.1 as well.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Feb 2022 19:15:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/compressing-sde-database/m-p/1147679#M43861</guid>
      <dc:creator>TylerDuffyETL</dc:creator>
      <dc:date>2022-02-24T19:15:57Z</dc:date>
    </item>
  </channel>
</rss>

