<?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 Archriving and Unique IDs in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/archriving-and-unique-ids/m-p/1217962#M7908</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I need some guidance for Indexing with Archiving enabled. I am getting an error to apply a unique index to a table with Archiving enabled. I understand that in the Data Base there is a duplication of the ID because of Archiving. Any help with the three questions below would be awesome.&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the best practice for indexing a table with Archiving?&lt;/P&gt;&lt;P&gt;Does indexing index the whole table or just the un-archrived values (ex: GDB_TO_DATE = xx/xx/9999)?&lt;/P&gt;&lt;P&gt;&lt;EM&gt;edit: I looked at the Object ID index and it is not unique, so I am assuming indexing works at the database level. &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;If I make a unique Index with multiple values like unique_Id+GlobalID+GDB_TO_DATE does this help the performance of joins where only the unique_id is used? Or can I only index one column ex: just the unique_Id to help performance of a join?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 30 Sep 2022 17:41:52 GMT</pubDate>
    <dc:creator>JimWilliams</dc:creator>
    <dc:date>2022-09-30T17:41:52Z</dc:date>
    <item>
      <title>Archriving and Unique IDs</title>
      <link>https://community.esri.com/t5/geodatabase-questions/archriving-and-unique-ids/m-p/1217962#M7908</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I need some guidance for Indexing with Archiving enabled. I am getting an error to apply a unique index to a table with Archiving enabled. I understand that in the Data Base there is a duplication of the ID because of Archiving. Any help with the three questions below would be awesome.&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the best practice for indexing a table with Archiving?&lt;/P&gt;&lt;P&gt;Does indexing index the whole table or just the un-archrived values (ex: GDB_TO_DATE = xx/xx/9999)?&lt;/P&gt;&lt;P&gt;&lt;EM&gt;edit: I looked at the Object ID index and it is not unique, so I am assuming indexing works at the database level. &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;If I make a unique Index with multiple values like unique_Id+GlobalID+GDB_TO_DATE does this help the performance of joins where only the unique_id is used? Or can I only index one column ex: just the unique_Id to help performance of a join?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2022 17:41:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/archriving-and-unique-ids/m-p/1217962#M7908</guid>
      <dc:creator>JimWilliams</dc:creator>
      <dc:date>2022-09-30T17:41:52Z</dc:date>
    </item>
  </channel>
</rss>

