Comments
| SQL Plan Management in Oracle Database 11g Release 1 - Maintain consistent SQL performance regardless of changes in optimizer version, optimizer statistics, schema changes, system settings and SQL profile creation. |
Thomas said... It's very good article |
Ratnesh Pune said... really good article. |
karthik said... Much appreciated! |
Leo James said... Very well explained. Comprehensive but clear. |
Mohamed Amin said... Thank you very mush , I wan unable to understand it from Oracle New future books, but you make it more clear than oraclethanks again |
Abdo Allah said... You said "If the SQL plan baseline doesn't contain a matching plan, the optimizer evaluates the accepted plans in the SQL plan baseline and uses the one with the lowest cost"is there a conflict between the first and second part? First you said SQL plan doesn't contain a matching plan in SQL plan baseline . second you said the optimizer takes one with the lowest cost from SQL plan baseline Please clarify because I am confused. Thanks |
Tim... said... Hi.I've reworded it so I think you will understand it now. It meant when an accepted sql plan baseline is found that matches the plan the optimizer just produced. There may be other accepted sql plan baselines for the statement that do not match the plan just produced by the optimizer. Cheers Tim... |
Abdo Allah said... said... Thanks Tim , it is more clear nowThanks again |
Regis said... Nicely explained and very powerfull tool in SQL tuning...:)-Regis |
DO NOT ask technical questions here, that's what my forum is for!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!