Re: SQL query
From: Glenn <glen_mackay_at_yahoo.com>
Date: 17 Mar 2006 09:45:25 -0800
Message-ID: <1142617525.203732.197770_at_v46g2000cwv.googlegroups.com>
Date: 17 Mar 2006 09:45:25 -0800
Message-ID: <1142617525.203732.197770_at_v46g2000cwv.googlegroups.com>
Hi Mark,
That did the trick. It is still not as fast as using sysdate but certainly quicker then my method which would hang for minutes. The explain plan still shows a MERGE JOIN CARTESIAN which doesn't show with SYSDATE but response is acceptable. Thanks for your help.
Below is the EXPLAIN PLAN with the tables
Id | Operation | Name -------------------------------------------------------------- 0 | SELECT STATEMENT | 1 | TABLE ACCESS BY INDEX ROWID | GEAR_TAG_ISSUANCES 2 | NESTED LOOPS | 3 | NESTED LOOPS | 4 | HASH JOIN | 5 | MERGE JOIN CARTESIAN | 6 | TABLE ACCESS BY INDEX ROWID| AREAS 7 | INDEX RANGE SCAN | AREAS_UK1 8 | BUFFER SORT | 9 | TABLE ACCESS FULL | LICENCE_PARTICIPANTS 10 | INDEX FAST FULL SCAN | LICARE_PK 11 | TABLE ACCESS BY INDEX ROWID | PARTICIPANTS 12 | INDEX UNIQUE SCAN | PRTCPNT_PK 13 | INDEX RANGE SCAN | TAG_ISS_LIC_FK_IReceived on Fri Mar 17 2006 - 18:45:25 CET
