Re: Propagated composite keys or one surrogate key?

From: Danny Roosens <roosens>
Date: 1996/09/11
Message-ID: <5172n7$441c_at_news-s01.ny.us.ibm.net>#1/1


Hi,

As I think I understand it correctly ,
you will have difficulty in joining this last table with the one above it in the hierarchy Since this new-single key is not in the other tables, you will have to derive the join from this this key, thus the index on it will not be used --> performance loss.

DannY.
<adizon_at_mail.us.net> wrote:
>In normalizing tables, the primary key of a parent table is usually
>propagated to the child table. In a multi-level parent-child arrangement,
>the lowest-level child table could have a composite primary key
>consisting of several columns. What are the advantages and disadvantages
>of substituting a single column as the surrogate primary key in place of
>the inherited composite key?
>
>Thanks,
>Lito
>
>Lito Dizon
>adizon_at_us.net
>
Received on Wed Sep 11 1996 - 00:00:00 CEST

Original text of this message