RE: next baby step in SQL: start using join

Thank you for that excellent observation, Rick!  I will check out the SQL 
analyzer.

- Dan

--- "Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx> wrote:
> Dan,
> 
> As I understand the optimizer it starts with the WHERE clause and then
> proceeds to the JOIN clause in determining what indexes, views, files, etc.
> to use for the query.  I don't think it really makes a difference if the
> join is done in the WHERE clause or the JOIN clause.  
> 
> There are several people here who join using the WHERE clause because that's
> the way they learned.  It may also be easier to understand the WHERE as
> opposed to the intricacies of JOIN because, IMO, it more easily relates to
> the way we think of organizing the data.  IMHO the JOIN is more powerful and
> flexible.  But, I learned SQL using JOIN so it is more natural for me.
> 
> If you are using the new iSeries Express (previously Client Access Express)
> you can use the SQL analyzer in Ops Nav to check out your queries before
> running them.  Any query that will make it to production I run against the
> analyzer to determine the best way to construct the statement.  I have
> compared using JOIN and WHERE for the same statement and the analyzer
> returned the same results for both queries.
> 
> Just my thoughts,
> 
> Rick


__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com