Explore >> Select a destination
|
You are here 
|
blog.tanelpoder.com | ||
| | | | |
connor-mcdonald.com
|
|
| | | | | When I'm troubleshooting, a common workflow for me isextract a problematic SQL statement from V$SQL or V$SQLSTATS or an AWR report.drop the SQL text into SQL Developer or VS Code so that I can format it into a more readable format.That was starting to frustrate me so I thought: "Why not have a SQL Formatter... | |
| | | | |
jonathanlewis.wordpress.com
|
|
| | | | | In an earlier articleI described how dbms_xplan.display_cursor() could be used to query memory to find the execution plans (and row source statistics) of recently executed SQL. In 9i, you have to use your own SQL to get the equivalent results. If you do, you should avoid using the "traditional" hierarchical type of query that you... | |
| | | | |
tanelpoder.com
|
|
| | | | | Some time ago I wrote a post about how COUNT(*) and COUNT(column) are semantically different things (link). Such queries may return different results if the column counted has NULLs in it. And the difference comes from that NULL is not a value, its rather a state which says value unknown or no value entered. So, you better understand how NULLs interact with your SQL constructs if you call yourself a DBA or a database developer ;-) - Linux, Oracle, SQL performance tuning and troubleshooting - consulting &... | |
| | | | |
blog.jooq.org
|
|
| | | This can probably be found elsewhere as well, but here's a short wrap-up how to get the most out of your execution plans, quickly 1. Be sure the actual rows and time statistics are collected. You can do this with -- login as user sys alter system set statistics_level = all; 2. Execute your bad... | ||
