|
You are here |
tonyhasler.wordpress.com | ||
| | | | |
hourim.wordpress.com
|
|
| | | | | I like very much Tanel Poder snapper and Carlos Sierra SQLTXPLAIN. They represent valuable performance diagnostic tools. Unfortunately I am still waiting to find a customer site where I will be allowed or granted necessary privileges to install and to use them. There are client sites where I have been asked to tune queries without... | |
| | | | |
orastory.wordpress.com
|
|
| | | | | There have been some interesting posts from Marcin Przepiorowski and Kerry Osborne about mapping sql plan management (spm) baselines to a corresponding sql id. The key to sql plan baselines (DBA_SQL_PLAN_BASELINES) is SIGNATURE. And why signature? It's not just another change to the key to identifying sql statements (HASH_VALUE -> (NEW_)HASH_VALUE / OLD_HASH_VALUE -> SQL_ID).... | |
| | | | |
savvinov.com
|
|
| | | | | In this post, I continue on the topic of examining SQL plans. I will talk about one DBMS_XPLAN function, DISPLAY_CURSOR (because it's probably the most useful one when troubleshooting ongoing performance issues, and also because other functions have a lot of similiarity to it). I will discuss frequently used options and some common problems. Preparation... | |
| | | | |
tanelpoder.com
|
|
| | | Update: As this original article is from 2007, there are better options available in the modern times for example DBMS_UTILITY.EXPAND_SQL_TEXT as explained by Maria Colgans blog entry here. If you have been involved in tuning SQL code which you have never seen before, you are probably familiar with the challenges of understanding what the code is trying to do. This can be especially time consuming when the SQL references lots of views, which reference views, which reference more views etc. So there may ... | ||