Re: Myltiple surrogate keys in one table!

>> Since both of the "original operational primary keys" allow nulls
in the
data warehouse, they do not qualify as candidate keys of any kind in that
context nor do they qualify as component columns in a compound candidate
key. Isn't it true that in this example the only candidate key is the new
surrogate key? <<

I would agree. In the merger I saw was a British and an American welding equipment suppliers who had designed their own inventory systems and catalog numbers. There were also problems about ISO versus American measurement units, packaging things by 10's or 12's, etc. The final solution was to set up a conversion table which would convert one catalog number to the other where they could. Received on Sun Jul 15 2001 - 03:19:11 CEST