|
You are here |
tanelpoder.com | ||
| | | | |
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. | |
| | | | |
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. | |
| | | | |
mauro-pagano.com
|
|
| | | | | When upgrading a database sometime you find that one or more SQLs run slower because ofa new and suboptimal execution plan. Usually the number of those SQLs is pretty small compared to the overall workload but it's not straightforward to understand what caused the plan change so even a small number can become tricky to... | |
| | | | |
jonathanlewis.wordpress.com
|
|
| | | Another little warning for those about to upgrade from 9i to 10g. Some hints will change their behaviour. Consider the following SQL. By default if Oracle cannot unnest a subquery it postpones execution of that subquery to the end of the execution plan. I've used the no_unnest hint in the subquery to stop Oracle from... | ||