<?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 Creating Attribute Index - UNIQUE, ASCENDING in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/creating-attribute-index-unique-ascending/m-p/416822#M23792</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am having problems creating an attribute index on file geodatabase tables that are UNIQUE and ASCENDING.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The FGDB tables contains data that originated from an ArcSDE-SQL Server database. It had indexes on the primary key fields (all character) that according to the table properties dialog in ArcCatalog are all UNIQUE and sorted in ASCENDING order.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After copying some of the data to new tables in a file geodatabase, I have been unable to duplicate the indexes in the file geodatabase. I have tried this under 9.3.1 and 10.0 with the same results. I have tried this through ArcToolbox, through the table properties/indexes dialog and through scripting. I've tried it with several different tables and file geodatabases. No error messages, but the resulting indexes always ends up being &lt;/SPAN&gt;&lt;STRONG&gt;NON_UNIQUE&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I thought perhaps there was a problem with creating unique indexes on a character or text field, so I tried creating a new field (LONG) and calculating it equal to the OBJECTID. I wasn't able to create a UNIQUE index on that field either.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The last thing I tested was using a personal geodatabase and guess what, it works fine. The only problem is that I can't use a personal geodatabase because of size limitations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any suggestions? Am I worrying about nothing? It seems that with a large database it would be important to have the correct type of index.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-Steve&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Sep 2012 15:39:16 GMT</pubDate>
    <dc:creator>StevePeaslee</dc:creator>
    <dc:date>2012-09-27T15:39:16Z</dc:date>
    <item>
      <title>Creating Attribute Index - UNIQUE, ASCENDING</title>
      <link>https://community.esri.com/t5/data-management-questions/creating-attribute-index-unique-ascending/m-p/416822#M23792</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am having problems creating an attribute index on file geodatabase tables that are UNIQUE and ASCENDING.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The FGDB tables contains data that originated from an ArcSDE-SQL Server database. It had indexes on the primary key fields (all character) that according to the table properties dialog in ArcCatalog are all UNIQUE and sorted in ASCENDING order.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After copying some of the data to new tables in a file geodatabase, I have been unable to duplicate the indexes in the file geodatabase. I have tried this under 9.3.1 and 10.0 with the same results. I have tried this through ArcToolbox, through the table properties/indexes dialog and through scripting. I've tried it with several different tables and file geodatabases. No error messages, but the resulting indexes always ends up being &lt;/SPAN&gt;&lt;STRONG&gt;NON_UNIQUE&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I thought perhaps there was a problem with creating unique indexes on a character or text field, so I tried creating a new field (LONG) and calculating it equal to the OBJECTID. I wasn't able to create a UNIQUE index on that field either.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The last thing I tested was using a personal geodatabase and guess what, it works fine. The only problem is that I can't use a personal geodatabase because of size limitations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any suggestions? Am I worrying about nothing? It seems that with a large database it would be important to have the correct type of index.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-Steve&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2012 15:39:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/creating-attribute-index-unique-ascending/m-p/416822#M23792</guid>
      <dc:creator>StevePeaslee</dc:creator>
      <dc:date>2012-09-27T15:39:16Z</dc:date>
    </item>
    <item>
      <title>Re: Creating Attribute Index - UNIQUE, ASCENDING</title>
      <link>https://community.esri.com/t5/data-management-questions/creating-attribute-index-unique-ascending/m-p/416823#M23793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Steve,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unique indexes are not supported on File Geodatabases.&amp;nbsp; See the section Unique Indexes &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://resources.arcgis.com/en/help/main/10.1/index.html#//005s00000011000000" rel="nofollow" target="_blank"&gt;here&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2012 16:00:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/creating-attribute-index-unique-ascending/m-p/416823#M23793</guid>
      <dc:creator>JakeSkinner</dc:creator>
      <dc:date>2012-09-27T16:00:27Z</dc:date>
    </item>
    <item>
      <title>Re: Creating Attribute Index - UNIQUE, ASCENDING</title>
      <link>https://community.esri.com/t5/data-management-questions/creating-attribute-index-unique-ascending/m-p/416824#M23794</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks Jake. MyBad for not looking a little harder. The AddIndex_management tool documentation doesn't mention any of those restrictions and in fact uses a file geodatabase in their example code.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-Steve&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Sep 2012 11:36:33 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/creating-attribute-index-unique-ascending/m-p/416824#M23794</guid>
      <dc:creator>StevePeaslee</dc:creator>
      <dc:date>2012-09-28T11:36:33Z</dc:date>
    </item>
  </channel>
</rss>

