August 7, 2012 at 2:47 am
Can a table have two primary keys
August 7, 2012 at 2:51 am
No
You can have a composite PK that consists of two (or more) keys but not two PK's
==========================================================================================================================
A computer lets you make more mistakes faster than any invention in human history - with the possible exceptions of handguns and tequila. Mitch Ratcliffe
August 7, 2012 at 2:52 am
Two individual primary keys - No
A primary key which spans multiple columns - Yes
What is it your trying to acheive?
Could get cleaver and put in a UNIQUE NONCLUSTERED index on the second column, just ensure that the column cannot accept nulls, and you get more or less the same result.
August 7, 2012 at 6:41 am
No.You can't add 2 primary key in a table.Instead u can add Unique key which accept null value in it.
August 7, 2012 at 7:28 am
rajprabuit (8/7/2012)
No.You can't add 2 primary key in a table.Instead u can add Unique key which accept null value in it.
But if the OP wants it to act like a primary key, you would want to ensure that the column is not nullable as a PK won't accept a NULL value.
August 7, 2012 at 9:15 am
Sounds like an interview or a homework question to me. 😀
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
August 7, 2012 at 9:44 am
Could be a test question.
A decade ago when I taught Database Theory, my tests were take home week long projects.
25 T/F
25 Multiple Choice
25 Fill in the blank
25 point Essay question.
During each week long test, it was open book, open notes, open internet. If they had come here for help, I was fine with it. Real world, we get to use google. I didn't see the harm in it. Still don't. I think the most annoying thing about MCITP exams is the need to memorize a bunch of stuff I could look up in little to no time at all.
I seriously think the number of questions should be increased dramatically, but the internet should be availalbe. If you can get enough correct in 2 hours or whatever, then you get the cert. 🙂
August 7, 2012 at 7:25 pm
seshu67 (8/7/2012)
Can a table have two primary keys
By absolute definition, no. That's why it's called a "Primary" key and there can only be one primary.
In all practicality, yes. You can create a UNIQUE constraint on a NOT NULL column and for all practical intent and purposes it works the same way as a Primary Key. It's what some folks call an "AK" or "Alternate Key".
If this is for an interview, be sure to mention that the PK does NOT have to be the clustered index. You can only have one clustered index.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 12, 2013 at 6:39 am
seshu67 (8/7/2012)
Can a table have two primary keys
In principle, yes. In practice it depends on what special functions or properties you want to assign to a primary key.
In the relational model a key is a minimal superkey - irreducibly unique and not permitting nulls. You can have more than one of those per relation. By convention when there is more than one such key then one of the keys is designated a "primary" one. But that primary designation doesn't make it "special" in any prescribed or fundamental respect. The choice and the difference (if any) between a primary key and a non-primary key is up to you.
Perhaps what you meant to ask is whether SQL's PRIMARY KEY constraint can be used more than once per table. The answer is no. It is an in-built limitation of SQL that PRIMARY KEY can only be used once per table. As Jeff says, you can use a UNIQUE constraint instead and that usually achieves the same things so the restriction on only having one PRIMARY KEY constraint per table isn't necessarily a serious limitation.
August 12, 2013 at 12:31 pm
seshu67 (8/7/2012)
Can a table have two primary keys
Absolutely no, period. The fact that separate unique constraints can be defined does not make them primary keys as well.
Similarly, a table could have 999 unique constraints that didn't allow nulls but not have a primary key.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
August 12, 2013 at 11:08 pm
ScottPletcher (8/12/2013)
seshu67 (8/7/2012)
Can a table have two primary keysAbsolutely no, period. The fact that separate unique constraints can be defined does not make them primary keys as well.
Similarly, a table could have 999 unique constraints that didn't allow nulls but not have a primary key.
Technically speaking and by definition, I absolutely agree. I think the OP was really asking if it were possible to have more than one non-null unique index on a table. Of course, the answer there is "Yes" and it's a fairly common practice when it comes to things like ISO standard lookup tables.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply