<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 Wagner Crivelini
»
SQL & the JOIN Operator
99 posts, Page 10 of 10
««
«
6
7
8
9
10
SQL & the JOIN Operator
Rate Topic
Display Mode
Topic Options
Author
Message
Paul White
Paul White
Posted Sunday, February 27, 2011 7:33 PM
SSChampion
Group: General Forum Members
Last Login: Today @ 4:22 PM
Points: 10,990,
Visits: 10,542
Jeff Moden (2/27/2011)
Isn't this a bit like the article you wrote on designing databases? While I agree with all the things you've stated, entire books have been written on how to join and all the caveates that occur when dupes are present, etc, ad infinitum. This article is a good
introduction
to joins... it's not the final word just like your introduction to designing databases isn't and wasn't intended to be the final word. Think about it...
The parallels weren't lost on me, no. That's no reason not to comment though, is it?
Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #1070261
wagner crivelini
wagner crivelini
Posted Monday, February 28, 2011 3:47 AM
SSC Rookie
Group: General Forum Members
Last Login: Wednesday, January 30, 2013 10:57 AM
Points: 28,
Visits: 173
SQLkiwi (2/27/2011)
Jeff Moden (2/27/2011)
Isn't this a bit like the article you wrote on designing databases? While I agree with all the things you've stated, entire books have been written on how to join and all the caveates that occur when dupes are present, etc, ad infinitum. This article is a good
introduction
to joins... it's not the final word just like your introduction to designing databases isn't and wasn't intended to be the final word. Think about it...
The parallels weren't lost on me, no. That's no reason not to comment though, is it?
Well, Paul, I agree with most of your observations, but Jeff is right: the purpose of this article is to introduce the newbie to a new world, SQL Joins.
If we were talking about motor vehicles instead of SQL, the articles could focus on strollers as well as in Ferraris. I'm focusing on stroller drivers here and I think it would be pointless for this audience to hear some many important details at this moment.
Post #1070398
Paul White
Paul White
Posted Monday, February 28, 2011 5:42 AM
SSChampion
Group: General Forum Members
Last Login: Today @ 4:22 PM
Points: 10,990,
Visits: 10,542
wagner crivelini (2/28/2011)
Well, Paul, I agree with most of your observations, but Jeff is right: the purpose of this article is to introduce the newbie to a new world, SQL Joins.
Ok, I hope the criticisms were taken in the constructive spirit they were intended.
Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #1070440
robmullins
robmullins
Posted Monday, February 28, 2011 6:17 AM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, October 05, 2011 7:45 AM
Points: 5,
Visits: 24
I was just going over this in my class, but you explain it much better! Great work! Out of curiosity, I have been hammered on calling it a 'relation' instead of a 'table'. I know the terms are somewhat interchangeable but is there a hard-fast rule for what we call them?
Thanks in advance.
Post #1070460
wagner crivelini
wagner crivelini
Posted Monday, February 28, 2011 6:23 AM
SSC Rookie
Group: General Forum Members
Last Login: Wednesday, January 30, 2013 10:57 AM
Points: 28,
Visits: 173
rob
relation is a term we generally use in academic environment and I guess this was the word Ed Codd used when he define the basics for relational modeling.
in day-top-day business, we assume the word TABLE describing the same (or roughly the same) concept.
Post #1070463
robmullins
robmullins
Posted Monday, February 28, 2011 6:26 AM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, October 05, 2011 7:45 AM
Points: 5,
Visits: 24
Gotcha! So more of an Ivory Tower nomenclature. Thanks for the speedy clarification.
Post #1070465
Jeff Moden
Jeff Moden
Posted Monday, February 28, 2011 7:36 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:51 PM
Points: 32,923,
Visits: 26,811
SQLkiwi (2/27/2011)
Jeff Moden (2/27/2011)
Isn't this a bit like the article you wrote on designing databases? While I agree with all the things you've stated, entire books have been written on how to join and all the caveates that occur when dupes are present, etc, ad infinitum. This article is a good
introduction
to joins... it's not the final word just like your introduction to designing databases isn't and wasn't intended to be the final word. Think about it...
The parallels weren't lost on me, no. That's no reason not to comment though, is it?
Heh... you're absolutely correct. I read more into it and you were a whole lot nicer about it than that other fellow. Thanks, Paul.
--Jeff Moden
"
RBAR
is pronounced "ree-bar" and is a "Modenism" for "
R
ow-
B
y-
A
gonizing-
R
ow".
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Post #1070523
Mike M - DBA2B
Mike M - DBA2B
Posted Wednesday, March 02, 2011 1:59 PM
SSC Veteran
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 1:12 AM
Points: 207,
Visits: 531
Excellent job, Wagner!
This reminds me of the first truly useful article on SQL that I found back in 199...7, I think. It was a beautifully detailed article describing normalization techniques to 3NF. This would have been a grand companion to it (all those years ago...) when I first started in the field. I plan to use this article when I explain these concepts to friends and coworkers who want to understand how JOINs work.
Bravo!
---Mike<G>
Post #1072194
Todd.Everett
Todd.Everett
Posted Saturday, March 26, 2011 8:24 AM
Forum Newbie
Group: General Forum Members
Last Login: Friday, April 19, 2013 8:25 AM
Points: 4,
Visits: 38
A real world application of cross join is to generate the results of applying databased rules to the row occurrences they apply to. For example, I have an application that tracks the set up of standard AD Groups for database schemas. I have the rules for these groups modeled in tables, and then cross join the rules with the schemas to generate a result set that applies each rule to each schema. I output this result set to a tracking table so I can track the set up of all these AD groups. This of course is only effective because there are a small number (less than 100) of schemas for which to manage a small number of AD groups (around 8 per schema).
Post #1084441
« Prev Topic
|
Next Topic »
99 posts, Page 10 of 10
««
«
6
7
8
9
10
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.
