Discussion on the topic:
http://www.sqlmag.com/Forums/messageview.cfm?catid=12&threadid=5819
Basically, if you have not other key identified, then it is fine to
use. However, during normalization PK's will be defined and identity will
not be necessary in a lot of cases.
To keep the so called "guru's" happy, do not overuse them; only use
them where they make sense. The "guru's" just want you to know that you do
not have to use them in everything because the keys can be created by using
the distinct data in the table. If your tables are normalized, you will
have no repeat data and therefore the distinct part of the data will be your
PK. However, I think that they are needed in most schemas and I think it
narrow minded to think that they should do away with it.
Jacob
-----Original Message-----
From: Michael T. Tangorre [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 9:49 AM
To: SQL
Subject: Keys and Data Types
I am working on a new DB design for a CFMX app and was doing a little
refresher research on keys and data types and ran across this quote from
former SQL Server project manager Ron Soukup,
"Identity primary keys are for people who believe there's never time to
design a table right but there's always time to do it over."
In another related article, another MS SQL guy says that the only reason
identity made it into SQL server was because of Access.... (not a direct
quote).
Anyone care to comment?
Mike
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=6
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=6
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community.
http://www.fusionauthority.com/ads.cfm
