UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Composite Indexes vs. Composite Primary Keys    
 
   
J.D.
post Apr 23 2004, 01:49 PM
Post#1


UtterAccess VIP
Posts: 4,506
Joined: 31-January 00
From: Columbus, OH USA


You will often hear that Composite or Multi-field Primary Keys is a poor design technique and usually violates the 1st normal form of Normalization. Typically it is recommended to use a composite Index instead to accomplish the effect of the combination of 2 or more fields to create a unique record. The problem is it's not often explained how. The attached db does just that. It walks you through the bad design of a composite PK, the Inproved design of adding an Autonumber Field, and ultimately the best design of having a single, autonumber primary key and a composite Index.
Hope you find this helpful,
Attached File(s)
Attached File  CompositeIndexExample.zip ( 26.73K )Number of downloads: 402
 
Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    14th December 2017 - 01:08 AM