Natural join in SQL Server
No, and thank the lucky stars
I can't believe that you'd want the engine to guess the JOIN for you
Related links:
- SQL Server - lack of NATURAL JOIN / x JOIN y USING(field)
- is NATURAL JOIN any better than SELECT FROM WHERE in terms of performance ?
Edit, to explain why
- The JOIN (whether USING or ON) is clear and explicit
- I should be able to name my columns for the entity stored in the table, without worrying about what a column is called in another table, without NATURAL JOIN side effects
Quoting Bill Karwin in this excellent answer:
I never use NATURAL JOIN because I don't like the possibility that the join could do something I don't intend just because some column name exists in both tables.
MS SQL does not support natural join, neither join using (). You have to explicitly write down all your attributes used in the join.
If the datamodel changes, you have to change all "natural join" written by hand and make sure your join condition is ok again.
I wouldn't expect to see it any time soon. A Connect suggestion from 2006 has very little info other than:
Thanks for your feedback. We will look into your request for one of the upcoming releases.
And has only received ~30 upvotes