Chris solution will work 🙂

Easy one to the end of week 😛

Hugo Kornelis (5/2/2013)

---

Good question, though I'm surprised that, apparently, people are doing this wrong. Since you'll be rewarded by an error message when you try, I don't understand how people...

Good basic question Vinay 🙂

+1 :-):-P

Sergiy (4/29/2013)

---

Thanks everyone for positive feedback.

As you can guess the question came from practical experience when developers were puzzled with "odd" behaviour of SQL Server.

Had to build this sample script...

Welcome back Lokesh, after a long time I see you man :-P;-)

Thanks for the good question 🙂

Nice question 🙂

PaulB-TheOneAndOnly (4/27/2013)

---

Fact is, you already have those books so I would go ahead and use them.

Plenty of information in the net about new/deprecated features between SQL Server versions therefore, I...

malleswarareddy_m (4/26/2013)

---

Thanks for nice question.

---Statement 1

CREATE TABLE #table1

(

ID int PRIMARY KEY,

Name varchar(20)

CONSTRAINT UN_Name UNIQUE(Name)

);

CREATE TABLE #table2

(

ID int PRIMARY KEY,

PersonName varchar(30) REFERENCES #table1(Name)

);

go

select * from #table1

select * from...

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?...

Thanks a lot cadavre for such a excellent explanation 🙂

Kingston Dhasian (4/26/2013)

---

Try creating a UNIQUE KEY constraint with both the columns on GV_Voucher table.

Your FOREIGN KEY constraint in GV_ReceivedOffice table should again be based on these 2 columns.

ALTER TABLE...

Kingston Dhasian (4/26/2013)

---

Try creating a UNIQUE KEY constraint with both the columns on GV_Voucher table.

Your FOREIGN KEY constraint in GV_ReceivedOffice table should again be based on these 2 columns.

ALTER TABLE...