|
Re: Analysing sql query [message #65793 is a reply to message #65785] |
Fri, 24 December 2004 01:50 |
Milind Deshpande
Messages: 93 Registered: May 2004
|
Member |
|
|
Hi,
I think the first step is to identify the writing of SQL. A bad written SQL will never give you good result, so if you feel that some changes are required do them.
After that identify the execution plan of the query for Index usage and Full table scan etc. My statement for Index usage doesnt mean that everytime Index scan is better than Full table scan.
You identify the Cost, Card and Bytes fetched by the query and proceed further for Tuning them.
Tuning is an art that needs a persons commonsense and expertise to identify where what is required.
Hope this helps.
Milind.
|
|
|