Re: Inserting a new PK into an existing table

joel garry wrote:

> Agree with natual/surrogate post by Daniel - except, SSN is not
> guaranteed unique! (The problem really being insufficient analysis of
> natural keys).
>
> jg
> --
> @home.com is bogus.
> http://dizwell.com/migforum/index.php?topic=189.0

SSN is in most situations. It certainly meets the needs of insurance companies. But you might want to do a two-field PK with SSN and DOB.

I like to use it because (A) I've never seen a duplicate and (B) if I saw one I'd like it to generate an error so I could call security.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org