Re: problem using identity column as primary key
From: Louis Davidson (dr_dontspamme_sql_at_hotmail.com)
Date: 02/25/04
- Next message: Louis Davidson: "Re: problem using identity column as primary key"
- Previous message: Guy Brom: "Re: Serious issue after maintance plan"
- In reply to: Bob Boran: "Re: problem using identity column as primary key"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Feb 2004 08:53:08 -0600
Amen, with only one caveat:
> Now, does that mean we don't also look for a natural key? No, a natural
key
> is still identified (if it is available) and a Unique constraint is
applied
> to it to enforce that rule.
If you don't have a natural key, you have exactly the thing that Joe
suggests, a record number.
Louis
-- ---------------------------------------------------------------------------- ----------- Louis Davidson (drsql@hotmail.com) Compass Technology Management Pro SQL Server 2000 Database Design http://www.apress.com/book/bookDisplay.html?bID=266 Note: Please reply to the newsgroups only unless you are interested in consulting services. All other replies will be ignored :) "Bob Boran" <mcsdsmurf@hotmail.com> wrote in message news:enhTZlv%23DHA.552@TK2MSFTNGP11.phx.gbl... > You obviously feel very strong about this issue. > Please lean back on this couch for a minute and lets talk about it. > Tell me about your days as a young DBA. Any early tramas that may have left > you feeling that artificial primary keys are inadequite? Let me turn on > this soft soothing music to help calm your troubled spirit. > > There, now that your breathing has returned to normal.. > > I am not going to pretend that I have spent years getting a masters or > doctorate in Database Design. I will even admit up-front that I don't even > have a CS degree. But what I do have is 10 years of experience designing, > implementing and maintaining enterprise databases for my clients. (yes, go > ahead and make your negative remark here, I will even leave space) > ------------ > This space reserved for Celco > > > > ----------- > Ok, now that you are done. > > My experience has taught me that using an artificial PK in every table is > the safest, easiest, most maintainable design technique for today's large > databases. A nice clean number that requires very little storage space, > something that can be easily used as a FK without causing potential > integrity issues when data needs to be update, something that I know is > unique without having to use 2-10 columns looking for a natural key, and > most of all consistency in my design model. > Now, does that mean we don't also look for a natural key? No, a natural key > is still identified (if it is available) and a Unique constraint is applied > to it to enforce that rule. > > I will stop there in order to keep my post long enough to say what needed to > be said, but short enough to be readable. > > >
- Next message: Louis Davidson: "Re: problem using identity column as primary key"
- Previous message: Guy Brom: "Re: Serious issue after maintance plan"
- In reply to: Bob Boran: "Re: problem using identity column as primary key"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
