| explain plan [message #65305] |
Wed, 28 July 2004 20:20  |
Jay
Messages: 127
Registered: October 1999
|
Senior Member |
|
|
Dear All,
I have a SQL query, whose explain plan is shown below. Can you please let me know, whether the following explain plan is a good plan or not? if not then where is the problem.
SELECT STATEMENT, GOAL = CHOOSE
SORT GROUP BY 0
NESTED LOOPS 1
NESTED LOOPS 2
NESTED LOOPS 3
NESTED LOOPS 4
TABLE ACCESS BY INDEX ROWID JAY T_CLAIM 5
INDEX RANGE SCAN JAY JKN_T_CLAIM 6
TABLE ACCESS BY INDEX ROWID JAY T_CLAIM_BASE 5
INDEX UNIQUE SCAN JAY PK_T_CLAIM_BASE 8
TABLE ACCESS BY INDEX ROWID JAY T_POLICY_BASE 4
INDEX UNIQUE SCAN JAY PK_T_POLICY_BASE 10
TABLE ACCESS BY INDEX ROWID JAY T_CLAIM_INSTALLMENT 3
INDEX RANGE SCAN JAY JKN_T_CLAIM_INSTALLMENT 12
TABLE ACCESS BY INDEX ROWID JAY T_CLAIM_DETAILS_BASE 2
INDEX UNIQUE SCAN JAY PK_T_CLAIM_DETAILS_BASE 14
Hope you will let me know.
Thanks,
Jay.
|
|
|
|
| Re: explain plan [message #65308 is a reply to message #65305] |
Thu, 29 July 2004 05:23  |
shoblock
Messages: 325
Registered: April 2004
|
Senior Member |
|
|
without actually knowing the actual sql, the number of records in each table, whether the indexes used are on joined columns or comparisons to variables (scalars), and many other things, I'll say "sure, it looks good"
The real question to you is: how does it perform? Elapsed time is much more meaningful than an explain plan, the cost, or any other info provided by sqltrace. After all, if it's fast, who cares about anything else!
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
