<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Timothy Claason
»
Decoupling in Relational Databases
99 posts, Page 1 of 10
1
2
3
4
5
»
»»
Decoupling in Relational Databases
Rate Topic
Display Mode
Topic Options
Author
Message
timclaason
timclaason
Posted Monday, March 01, 2010 9:33 PM
Grasshopper
Group: General Forum Members
Last Login: Thursday, April 18, 2013 8:56 AM
Points: 22,
Visits: 140
Comments posted to this topic are about the item
Decoupling in Relational Databases
Post #874846
Martin Widmer
Martin Widmer
Posted Tuesday, March 02, 2010 12:49 AM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, June 20, 2012 7:32 AM
Points: 1,
Visits: 17
The article is of course correct but 'decoupling databases' is not what it is about. What you describe is the very basics of database design. And the tabels are relation tables, not bridge tables... So nothing is being decoupled here, just properly designed.
Post #874901
james.prendergast
james.prendergast
Posted Tuesday, March 02, 2010 12:55 AM
Forum Newbie
Group: General Forum Members
Last Login: Monday, April 01, 2013 5:46 PM
Points: 1,
Visits: 20
I have to agree that this article is both mis-named and really a no-brainer. Just good design practice. There is really no simpler way of implementing many-to-many relationships in relational databases
Post #874902
Gary Varga
Gary Varga
Posted Tuesday, March 02, 2010 1:36 AM
Hall of Fame
Group: General Forum Members
Last Login: Yesterday @ 7:40 AM
Points: 3,541,
Visits: 1,134
My understanding is that in this standard relational database design pattern (as highlighted by the previous posters) and what the article refers to as a 'bridge table' is commonly referred to as a 'link table'.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #874924
sqlusers
sqlusers
Posted Tuesday, March 02, 2010 2:54 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: 2 days ago @ 1:34 AM
Points: 196,
Visits: 464
Hi Timothy,
Normalization and decoupling are one and the same?
Post #874950
Gary Varga
Gary Varga
Posted Tuesday, March 02, 2010 3:05 AM
Hall of Fame
Group: General Forum Members
Last Login: Yesterday @ 7:40 AM
Points: 3,541,
Visits: 1,134
sqlusers (3/2/2010)
Hi Timothy,
Normalization and decoupling are one and the same?
Just to butt in, I would say that normalisation is the standard way of decoupling data in a relational database.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #874959
bill.sugden
bill.sugden
Posted Tuesday, March 02, 2010 3:06 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Wednesday, July 13, 2011 4:11 AM
Points: 113,
Visits: 144
Give the guy a break - this is aimed at newbies.
Right - it is a no-brainer for us grizzled database developers. I can add a little constructive criticism though Tim. Your link table has an IDENTITY column - why? If you create a composite key of your fk_user + fk_group columns (check out your naming as well) and set this as the PRIMARY KEY to this link table you are killing a couple of birds with one stone.
(1) You have eliminated a redundant column
(2) You have ensured that you are not duplicating USER-GROUP membership (PK uniqueness)
(3) You can either eliminate your duplicate checking SQL and let the UI layer deal with an error, or simplify your checking to ignore the error completely
Bill
Post #874960
Gary Varga
Gary Varga
Posted Tuesday, March 02, 2010 3:47 AM
Hall of Fame
Group: General Forum Members
Last Login: Yesterday @ 7:40 AM
Points: 3,541,
Visits: 1,134
bill.sugden (3/2/2010)
Give the guy a break - this is aimed at newbies.
Right - it is a no-brainer for us grizzled database developers. I can add a little constructive criticism though Tim. Your link table has an IDENTITY column - why? If you create a composite key of your fk_user + fk_group columns (check out your naming as well) and set this as the PRIMARY KEY to this link table you are killing a couple of birds with one stone.
(1) You have eliminated a redundant column
(2) You have ensured that you are not duplicating USER-GROUP membership (PK uniqueness)
(3) You can either eliminate your duplicate checking SQL and let the UI layer deal with an error, or simplify your checking to ignore the error completely
Bill
Bill,
I will say that I feel that most of the comments are constructive criticisms. Particularly as this is aimed at the more novice practitioner, we need to ensure the accuracy of the article. Personally, I don't think that terms such as 'no brainer' and 'newbies' helps but some people find them helpful descriptives. Interestingly, there is a recent thread discussing how to inform authors or errors, mistakes and corrections ([url=http://www.sqlservercentral.com/Forums/Topic872452-263-1.aspx][/url]).
Regards,
Gary
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #874985
ALZDBA
ALZDBA
Posted Tuesday, March 02, 2010 3:48 AM
SSCertifiable
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 2:17 AM
Points: 6,862,
Visits: 8,049
This is a good article that proves how normalization helps you design and maintain a database.
Johan
Jul 13
Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere
-
How to post Performance Problems
-
How to post data/code to get the best help
-
How to prevent a sore throat after hours of presenting ppt ?
"press F1 for solution", "press
shift
+F1 for urgent solution"
Need a bit of Powershell? How about
this
Who am I ?
Sometimes this is me
but
most of the time this is me
Post #874987
Jonathan AC Roberts
Jonathan AC Roberts
Posted Tuesday, March 02, 2010 4:15 AM
Old Hand
Group: General Forum Members
Last Login: Yesterday @ 4:50 AM
Points: 316,
Visits: 1,186
It's not decoupling but designing for resolving many-to-many releationships.
Post #874998
« Prev Topic
|
Next Topic »
99 posts, Page 1 of 10
1
2
3
4
5
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
