January 28, 2013 at 9:04 am
I want to know how order of joins executed in sql server. Suppose i have used 3 tables in join.
table1 JOIN table2 JOIN table3
Does sql server execute in same sequence as i have written, first get common data from table1 and table2 then rest result and table3?
As i know WHERE clause dont executed by sql in the sequence that we write in query, so it raise question for me does for join.
January 28, 2013 at 9:23 am
Not sure I understand the question here. Are you wanting to logically or how the actual internals work?
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
January 28, 2013 at 9:27 am
Yes, Because in one of my query, i am joining with 3 tables. And table 1 have the 1 million record, 2 Lakh and table3 have 10 thousands.
I am using inner join, so question came on my mind how order of join works. For the above case it is important to know.
January 28, 2013 at 9:31 am
purushottam2 (1/28/2013)
Yes, Because in one of my query, i am joining with 3 tables. And table 1 have the 1 million record, 2 Lakh and table3 have 10 thousands.I am using inner join, so question came on my mind how order of join works. For the above case it is important to know.
SQL query optimizer should (and most of the times it does) figure out the best sequence by itself.
Saying that, I used to follow my old custom to drive query from the smallest table/data set...
January 28, 2013 at 11:53 am
Eugene Elutin (1/28/2013)
purushottam2 (1/28/2013)
Yes, Because in one of my query, i am joining with 3 tables. And table 1 have the 1 million record, 2 Lakh and table3 have 10 thousands.I am using inner join, so question came on my mind how order of join works. For the above case it is important to know.
SQL query optimizer should (and most of the times it does) figure out the best sequence by itself.
Saying that, I used to follow my old custom to drive query from the smallest table/data set...
I believe the SQL Optimizer can change the join order for queries that use only inner joins. Once you start introducing Outer Joins the order of the joins matters and a different order of Outer Joins could produce a different result set.
(Now, im currently looking for the source i read this from but having difficulty finding it again. If i find it ill edit this post with a link to the source.)
For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw[/url]
Need to Split some strings? Jeff Moden's DelimitedSplit8K[/url]
Jeff Moden's Cross tab and Pivots Part 1[/url]
Jeff Moden's Cross tab and Pivots Part 2[/url]
January 29, 2013 at 9:30 am
CapnHector (1/28/2013)
Eugene Elutin (1/28/2013)
purushottam2 (1/28/2013)
Yes, Because in one of my query, i am joining with 3 tables. And table 1 have the 1 million record, 2 Lakh and table3 have 10 thousands.I am using inner join, so question came on my mind how order of join works. For the above case it is important to know.
SQL query optimizer should (and most of the times it does) figure out the best sequence by itself.
Saying that, I used to follow my old custom to drive query from the smallest table/data set...
I believe the SQL Optimizer can change the join order for queries that use only inner joins. Once you start introducing Outer Joins the order of the joins matters and a different order of Outer Joins could produce a different result set.
(Now, im currently looking for the source i read this from but having difficulty finding it again. If i find it ill edit this post with a link to the source.)
The optimizer can construct and use any execution plan that is logically equivalent to the T-SQL query, i.e., it can process joins in any order that yields the required result. The optimizer's entire purpose is to find the most efficient execution plan. It relies on statistics and metadata to make cost-based decisions about how to execute each query, and it almost always does an excellent job. We can get better execution plans by writing queries in a way that allows the optimizer to make full use of the resources available to it, though (read up on SARGable predicates for one example of this).
Jason Wolfkill
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply