<?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: Controlling Size of Historical tables? in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/controlling-size-of-historical-tables/m-p/1152597#M43905</link>
    <description>&lt;P&gt;Thanks for pointing me in that direction. The trim history tool looked promising, but both items are versioned as well.&lt;/P&gt;</description>
    <pubDate>Thu, 10 Mar 2022 15:15:27 GMT</pubDate>
    <dc:creator>JCGuarneri</dc:creator>
    <dc:date>2022-03-10T15:15:27Z</dc:date>
    <item>
      <title>Controlling Size of Historical tables?</title>
      <link>https://community.esri.com/t5/data-management-questions/controlling-size-of-historical-tables/m-p/1152576#M43903</link>
      <description>&lt;P&gt;In the process of cleaning up datasets we no longer use and looking at disk usage for an Enterprise geodatabase, I discovered that nearly half of the disk usage is coming from the historical tables of two frequently updated items, a feature class in a feature dataset and a table. These two items participate in a relationship class with each other. Between the two of them, the tables are taking up almost 95 GB, whereas the current data only takes up about 3 GB combined. Is there a way to keep the size of the historical tables in check without turning off geodatabase history?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2022 15:16:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/controlling-size-of-historical-tables/m-p/1152576#M43903</guid>
      <dc:creator>JCGuarneri</dc:creator>
      <dc:date>2022-03-10T15:16:31Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling Size of Historical tables?</title>
      <link>https://community.esri.com/t5/data-management-questions/controlling-size-of-historical-tables/m-p/1152584#M43904</link>
      <description>&lt;P&gt;There is whole help topic section on "history" that may be useful, check the table of contents to the right of this link&lt;/P&gt;&lt;P&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/archive-history.htm" target="_blank"&gt;Archive history—ArcGIS Pro | Documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;maybe something might be useful&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2022 14:33:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/controlling-size-of-historical-tables/m-p/1152584#M43904</guid>
      <dc:creator>DanPatterson</dc:creator>
      <dc:date>2022-03-10T14:33:18Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling Size of Historical tables?</title>
      <link>https://community.esri.com/t5/data-management-questions/controlling-size-of-historical-tables/m-p/1152597#M43905</link>
      <description>&lt;P&gt;Thanks for pointing me in that direction. The trim history tool looked promising, but both items are versioned as well.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2022 15:15:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/controlling-size-of-historical-tables/m-p/1152597#M43905</guid>
      <dc:creator>JCGuarneri</dc:creator>
      <dc:date>2022-03-10T15:15:27Z</dc:date>
    </item>
  </channel>
</rss>

