Natural keys on some databases require a full table scan for retrieval, meaning that indexes are not used, resulting in slower performance on data retrieval. Just putting a natural key with 3 or more columns in a table may result in significantly reduced performance.
John Davidson On Tue, Mar 16, 2010 at 1:01 PM, José F. Romaniello <[email protected]>wrote: > just in case you didn't see this before: > http://www.agiledata.org/essays/keys.html > > 2010/3/16 Corey Coogan <[email protected]> > > I'm trying to get my client to implement surrogate keys on their legacy >> database to make using an ORM more viable, among other reasons. I drafted a >> quick document discussing the points and weighing surrogate keys against >> natural keys. >> >> I'm hoping to get some feedback and comments on what's missing, inaccurate >> or should be removed. Any help is greatly appreciated. >> >> Thanks, >> Corey >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "nhusers" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<nhusers%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/nhusers?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
