Explore >> Select a destination
|
You are here 
|
jonathanlewis.wordpress.com | ||
| | | | |
www.bobbydurrettdba.com
|
|
| | | | | We have been discussing query tuning at work and I've come back to an example of the Oracle optimizer choosing the wrong plan due to an error in its calculation of the number of rows returned... | |
| | | | |
www.dbaglobe.com
|
|
| | | | | A blog about on new technologie. Hands-on note about Hadoop, Cloudera, Hortonworks, NoSQL, Cassandra, Neo4j, MongoDB, Oracle, SQL Server, Linux, etc. | |
| | | | |
nenadnoveljic.com
|
|
| | | | | Oracle's heuristics previously avoided considering fixed tables for Join Predicate Pushdown (JPPD) transformation, leading to suboptimal plans. Enforcing predicate pushing into the view with the PUSH_PRED hint was a workaround. Oracle addressed this in the 21c release, evaluating fixed tables for JPPD. | |
| | | | |
jonathanlewis.wordpress.com
|
|
| | | I've discussed the capabilities of the dbms_xplan package in a couple of posts already; and shown how useful it can be in two examples: understanding a problem with filter subquery selectivity and understanding why some Cartesian merge joins were appearing unexpectedly. Let me make a crucial point about execution plans (again): if you have a... | ||
