Oracle Tuning: Step 4 - Restructure
* Avoid the use of transformations in the WHERE clause
* Avoid using functions in WHERE clause
* Avoid expressions different data type conversions
* Avoid implicit data
* Write separate queries for specific tasks.
* Using UNION ALL
* Use EXISTS instead of IN for Subqueries
* Control access forms and order of the joins with hints
* Write the WHERE predicates using AND e = do not use LIKE as possible
Wednesday, April 23, 2008
How Long After Va Appraisal To Buy A House
Oracle SQL Tuning: Step 3 - Review Implementation plans
* The type of join should be appropriate to the number of rows to process
guide * The table is the best filter is
* Must be derived by next step the smallest number of rows
* The views must be used efficiently
* Examine the where clause from the rows processed at each table
* A Full Table Scan does not imply inefficiency
* Each table must be accessed efficiently
* should not Cartesian products exist that have not been made on purpose
* The type of join should be appropriate to the number of rows to process
guide * The table is the best filter is
* Must be derived by next step the smallest number of rows
* The views must be used efficiently
* Examine the where clause from the rows processed at each table
* A Full Table Scan does not imply inefficiency
* Each table must be accessed efficiently
* should not Cartesian products exist that have not been made on purpose
Subscribe to:
Posts (Atom)