November 19, 2002 at 9:08 pm
Hi all,
Is there any disadvantages of using Identity column as the only primary key? I've got a strong habit to set the primary key of all my tables to one identity column. This is because I think it's less overhead rather than creating the primary key according to business rules which may end up of having a composite primary key with many columns.
Another reason of doing it is that my Software Development team is using Code Generator tools and such a tool insisted to have all the tables had an identity key set.
Also, it's interesting, when I evaluate 3rd party Code Generators, almost all of the products insisted and suggested to use identity column in a table. Some of them refer this as a best practice in database design. At any point, I agree with that, I found that building application will become a lot easier too if I use identity especially for the PK_FK relationship.
So far so good, until I realize from the BOL that I can't use identity column in my table if I will make it a partitioned view. (any workarounds ?)
I need any opinions on this. Is there a major drawbacks of using identity which I might not reliaze?
Thanks in advance.
Hendry
November 20, 2002 at 3:50 am
Have a look at http://qa.sqlservercentral.com/forum/reviews.asp?CAT_ID=7&FORUM_ID=29&TOPIC_ID=1364&type=2&article=488
Simon Sabin
Co-author of SQL Server 2000 XML Distilled
http://www.amazon.co.uk/exec/obidos/ASIN/1904347088
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
November 21, 2002 at 2:44 am
Simon, Thanks for the link
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply