I am having problems creating an attribute index on file geodatabase tables that are UNIQUE and ASCENDING.
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.
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 NON_UNIQUE.
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.
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.
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.
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.
