Q
Problem solve Get help with specific problems with your technologies, process and projects.

Which order points to look at to understand output and improve execution of a query

Could you help me analyze information from "set autotrace on" when a query is executed? I mean, I know full table scans are heavy on big tables. But which order points should we look at to understand output and improve execution (e.g., consistent get statistics, costs at explain plans, full index scan steps, hash join steps?). Could you explain a little about output statistics?

Could you help me analyze information from "set autotrace on" when a query is executed? I mean, I know full table scans are heavy on big tables. But which order points should we look at to understand output and improve execution (e.g., consistent get statistics, costs at explain plans, full index scan steps, hash join steps?). Could you explain a little about output statistics?
You should try to reduce the amount of work done. Fewer consistent gets and fewer disk reads will improve performance. The best way to measure performance is to measure the amount of time a query takes to run. In SQL*Plus, issue a SET TIMING ON command, which will tell you the elapsed time for an operation. For more information, consult the Oracle Performance Tuning manual.

Dig Deeper on Oracle database performance problems and tuning

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close