Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Freddie
Starting Member
29 Posts |
 Posted - 2009-06-29 : 10:15:22
|
| Hello:Should a bridge table key contain the keys from other tables or should it have it's own sequential key?ThanksF. |
|
|
LoztInSpace
Aged Yak Warrior
940 Posts |
Posted - 2009-06-30 : 09:51:45
|
| In my opinion, just the FKs. If it has more additional rows than the usual sequence #, timestamp or whatever and you start to join to it in its own right (rather than it join to the other tables) then it has the potential for its own PK. Even if you do add the other key, remember to put at least a unique constraint & index on the 2 values you are joining.The 'every table must have a clustered index' brigade will disagree because of their assertion that, well, 'every table must have a clustered index' which sucks for these cases (which is why they are wrong).Apologies for the sidetrack! |
 |
|
|
Maysam
Starting Member
8 Posts |
Posted - 2009-07-02 : 17:06:05
|
| Its own Seq key. |
|
|
|
LoztInSpace
Aged Yak Warrior
940 Posts |
Posted - 2009-07-04 : 01:54:17
|
quote:
Originally posted by Maysam
Its own Seq key.
Why? |
|
|
|
|
|
|
BRIDGE TABLE