Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Show/Explain Query Plan

Re: Show/Explain Query Plan

From: Ng K C Paul <paulkcng_at_news.netvigator.com>
Date: 1998/09/19
Message-ID: <6u0lfe$r78$1@imsp009a.netvigator.com>#1/1

I think you can guess what is the execution path of SQL Server running the following query.

select * from table1 where col1 <> col1

Dan Guzman (nospamplease_guzmanda_at_mindspring.com) wrote:
: Ng K C Paul wrote in message <6tvoo6$dti$2_at_imsp009a.netvigator.com>...
: >I always think that the where clause is the row filtering criteria
: >
:
: By 'row filtering criteria', I meant column references in the where clause.
: The where clause in question contains only literals so it is the rows from
: the result set that are filtered, not individual table rows. No indexes
: will be taken into account in the generation of the execution plan
: because.there is no criteria placed on individual table rows.
:
: The point I was trying to make is that the query plan (at least with MSSQL
: Server 6.5) does not show that the boolean condition seems to be evaluated
: before the table scan actually takes place so the query will run
: instantaneously regardless of the size of the table as long as the condition
: is false. If condition is true, a table scan will occur, as it should due
: to the absence of row filtering criteria.
:
:
:
:
:
:
Received on Sat Sep 19 1998 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US