Here is a off the wall question. Whare are either the pros or cons of having
the same column in a table with both a primary key and foreign key?
I know that I can do this, because I tested it. But, I don't know if there
are good or bad affects from doing so.
thanksNo problem at all. In the Northwind database, check out the [Order Deta
ils]
table. Both ProductID and OrderID are foreign keys and both form the
primary key.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
.
"BillyDees" <BillyDees@.discussions.microsoft.com> wrote in message
news:2D2E6340-71BF-4FF0-B496-50D514C9D6B5@.microsoft.com...
Here is a off the wall question. Whare are either the pros or cons of having
the same column in a table with both a primary key and foreign key?
I know that I can do this, because I tested it. But, I don't know if there
are good or bad affects from doing so.
thanks|||Thank you Tom for the feedback.
Joe
"Tom Moreau" wrote:
> No problem at all. In the Northwind database, check out the [Order De
tails]
> table. Both ProductID and OrderID are foreign keys and both form the
> primary key.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
> ..
> "BillyDees" <BillyDees@.discussions.microsoft.com> wrote in message
> news:2D2E6340-71BF-4FF0-B496-50D514C9D6B5@.microsoft.com...
> Here is a off the wall question. Whare are either the pros or cons of havi
ng
> the same column in a table with both a primary key and foreign key?
> I know that I can do this, because I tested it. But, I don't know if there
> are good or bad affects from doing so.
> thanks
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment