![](//teradataforum.com/imgs/ptdfw1.gif) |
![](//teradataforum.com/imgs/ptdfw2.gif) |
Archives of the TeradataForum
Message Posted: Fri, 30 Mar 2007 @ 19:32:28 GMT
Subj: | | Order of inner joins alter plan |
|
From: | | Poston, Donna |
Hi all,
I have been working on a query that has enough conditions coded in the where that one of two possible secondary indexes could be used. The
optimizer has selected to use the secondary index where the volume retrieved is much greater than the other option.
The query has several inner joins against the sales table. Each inner join is to a derived table. When one of the inner joins is moved from
the top of the statement to the bottom, the plan will change to use the more efficient secondary index. Has anyone experienced this in the past?
Does the order of explicit inner joins make a difference and if so are there guidelines to follow.
Thanks in advance.
| |