Create Table

Question

Post reply

Create Table

kapil_kk

SSC-Insane

Points: 21316
More actions
April 25, 2013 at 9:03 pm

#276900

Comments posted to this topic are about the item Create Table
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
April 25, 2013 at 11:00 pm

This was removed by the editor as SPAM

Viewing 15 posts - 1 through 15 (of 29 total)

You must be logged in to reply to this topic. Login to reply

Dineshbabu Hall of Fame Points: 3220 More actions · Answer 1

Good Information..

--
Dineshbabu
Desire to learn new things..

Vinay Kumar SSCertifiable Points: 6099 More actions · Answer 2

Kapil, very good question. 🙂

Thanks
Vinay Kumar
-----------------------------------------------------------------
Keep Learning - Keep Growing !!!

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 3

Easy one to close off the week, thanks!

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Stuart Davies SSCoach Points: 19505 More actions · Answer 4

Koen Verbeeck (4/26/2013)
Easy one to close off the week, thanks!

+1 - thanks for the question

-------------------------------Posting Data Etiquette - Jeff Moden [/url]Smart way to ask a question
There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand (the world). There is no such thing as a dumb question. ― Carl Sagan
I would never join a club that would allow me as a member - Groucho Marx

Hugo Kornelis SSC Guru Points: 64790 More actions · Answer 5

I first focused on the reference to a unique constraint rather than the primary key, thinking that was the issue of the question. I almost got it wrong because of that, as I had first not given enough attention to the other details of the code.

I guess that many people will get this question right for the wrong reasons. (Many people think that a foreign key should always reference the primary key).

Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
Visit my SQL Server blog: https://sqlserverfast.com/blog/
SQL Server Execution Plan Reference: https://sqlserverfast.com/epr/

Vinay Kumar SSCertifiable Points: 6099 More actions · Answer 6

Hugo Kornelis (4/26/2013)
I first focused on the reference to a unique constraint rather than the primary key, thinking that was the issue of the question. I almost got it wrong because of that, as I had first not given enough attention to the other details of the code.
I guess that many people will get this question right for the wrong reasons. (Many people think that a foreign key should always reference the primary key).

Same happened with me, but suddenly i see the data type size and i got it. Actually i read this one few time ago, that's help me. 🙂

Thanks
Vinay Kumar
-----------------------------------------------------------------
Keep Learning - Keep Growing !!!

Thorpehall Mr or Mrs. 500 Points: 560 More actions · Answer 7

Can someone please point me towards the place where the documentation explains that a foreign key column must have the same length as the column that it references? I can't see it in the link to MSDN provided in the answer.

The Create Table documentation here: does say that that both columns must both be of the same data type, but it doesn't mention length.

ronmoses@gmail.com SSCarpal Tunnel Points: 4480 More actions · Answer 8

This is what I get for trusting that voice in my head that says, "No, that's way too obvious." :crazy:

ron

-----
a haiku...

NULL is not zero
NULL is not an empty string
NULL is the unknown

yogyogi97 SSC Veteran Points: 248 More actions · Answer 9

Thanks for good question.

I just looked at the syntax, column name and column data type and then length of column.

kapil_kk SSC-Insane Points: 21316 More actions · Answer 10

Mick Gillatt (4/26/2013)
Can someone please point me towards the place where the documentation explains that a foreign key column must have the same length as the column that it references? I can't see it in the link to MSDN provided in the answer.
The Create Table documentation here: does say that that both columns must both be of the same data type, but it doesn't mention length.

Sorry for that but I also didn't find that information that foreign key must have same length as referencing columns so in answer I placed the link of constraint.

I found this situation when I working on a script so think of put it as a QOTD!!

_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/

PChiragS SSCarpal Tunnel Points: 4965 More actions · Answer 11

PChiragS

SSCarpal Tunnel

Points: 4965

April 26, 2013 at 6:57 am

#1610325

Thanks for the question..Kapil

mtassin SSC-Insane Points: 23099 More actions · Answer 12

Hugo Kornelis (4/26/2013)
I first focused on the reference to a unique constraint rather than the primary key, thinking that was the issue of the question. I almost got it wrong because of that, as I had first not given enough attention to the other details of the code.
I guess that many people will get this question right for the wrong reasons. (Many people think that a foreign key should always reference the primary key).

nah, that one I had... I've had to do enough FK's to Unique constraints in my life to remember that lesson...

I'm just glad that I re-read it... and noticed the different column sizes.

--Mark Tassin
MCITP - SQL Server DBA
Proud member of the Anti-RBAR alliance.
For help with Performance click this link[/url]
For tips on how to post your problems[/url]

srienstr SSCrazy Points: 2435 More actions · Answer 13

I was initially leaning toward the right answer for the right reason, then talked myself out of it, thinking that SQL Server would be able to handle it. :hehe:

Of course, I also don't see why it can't implicitly handle the GROUP BY statement.

Puto me cogitare, ergo puto me esse.
I think that I think, therefore I think that I am.