With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.
Course Of The Month
4 days, 20 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
SQL JOIN syntax
Posted on 2012-12-25
When doing SQL JOINS is see two different syntax for what seems to be the same thing, one using the JOIN syntax and one not. See examples.
Code 1
SELECT Address.City, Name.NameFirst
from Address, Name
Where Address.AddressId = Name.AddressId
Code 2
SELECT Address.City, Name.NameFirst
from Address
join Name
on name.addressid = address.addressid
Needless to say there are many variations, but the fundamental difference seems to be using the FROM <table1>, <table2>
versus using JOIN <table2>
Even the variations of Left, Right, inner, outer seem easier managed with the Code 1 concept.
To me same Code 1 seems lots simpler.
Code 1
SELECT Address.City, Name.NameFirst
from Address, Name
Where Address.AddressId = Name.AddressId
Code 2
SELECT Address.City, Name.NameFirst
from Address
join Name
on name.addressid = address.addressid
Needless to say there are many variations, but the fundamental difference seems to be using the FROM <table1>, <table2>
versus using JOIN <table2>
Even the variations of Left, Right, inner, outer seem easier managed with the Code 1 concept.
To me same Code 1 seems lots simpler.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3 Comments
The question is, when and why would you need to use the JOIN syntax as both styles seem the same. And is it simply a matter of style? Just trying to learn best methods.
Active 2 days ago
Code1 and Code2 is identical for INNER JOINs.
The Code1 is older concept and not all SQL dialects allow to specify OUTER JOIN by operator in WHERE clause.
OTOH, Code1 allows CROSS JOIN which is not available in all SQL dialects supporting JOIN clause...
So, use the way which better fits to you and your SQL engine specifications. Everything else is a work for SQL optimization.
The Code1 is older concept and not all SQL dialects allow to specify OUTER JOIN by operator in WHERE clause.
OTOH, Code1 allows CROSS JOIN which is not available in all SQL dialects supporting JOIN clause...
So, use the way which better fits to you and your SQL engine specifications. Everything else is a work for SQL optimization.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed.
Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
Why is this different from all of the other step by step guides? Because I make a living as a DBA and not as a writer and I lived through this experience.
Defining the name:
When I talk to people they say different names on this subject stuff l…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Suggested Courses
Course of the Month4 days, 20 hours left to enroll
688 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.