MS Access table with KeyUID in two indexes.

rberke
rberke used Ask the Experts™
on
I just noticed that our database's largest table has two indexes that appear to do nearly the same thing:

Index Name    Field Name  Primary Unique IgnoreNulls
PrimaryKey     KeyUID          Yes        Yes      No
IndexKeyUID   KeyUID         No         No       No

I am tempted to delete IndexKeyUID.  Is that a bad idea?

In fact, I am not sure I know if the index name really matters.  Could it be called "George" and still accomplish the same thing?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
President / Owner
Most Valuable Expert 2017
Most Valuable Expert 2012
Commented:
<<I am tempted to delete IndexKeyUID.  Is that a bad idea?>>

 Nope, it's the field(s) that count.   You can delete it without issue.

Jim.
Jim Dettman (EE MVE)President / Owner
Most Valuable Expert 2017
Most Valuable Expert 2012

Commented:
and BTW, if you are enforcing RI, JET/ACE automatically created a hidden index on the child table, so if you've defined an index in a child table on the foreign key field, it's a dup and you can delete it.

 Another thing that will catch you; there is a feature in Access (look in options), that will automatically add an index if it see's a field with "ID", etc in it.   Do yourself a favor and turn the feature off.

Jim.
rberkeConsultant

Author

Commented:
Thanks for the tips
BTW  options>object designers > AutoIndex on Import/create   had ID;key;code;num

I deleted all 4.
rberke

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial