Outer Web | Explore

Explore >> Select a destination

You are here		nenadnoveljic.com Performance Problem with Incremental Statistics Calculation - All-round Database Topics
\|	\|	www.dbaglobe.com Donghua's Blog - DBAGlobe: How the Query Optimizer Chooses Execution Plans for Joins	9.5 parsecs away Travel
\|	\|	A blog about on new technologie. Hands-on note about Hadoop, Cloudera, Hortonworks, NoSQL, Cassandra, Neo4j, MongoDB, Oracle, SQL Server, Linux, etc.	9.5 parsecs away Travel
\|	\|	tonyhasler.wordpress.com Parallel partition scans \| Tony's Oracle Tips	10.1 parsecs away Travel
\|	\|	When a table is accessed by multiple members of a parallel query server set, the execution plan may show the use of block range granules (PX BLOCK ITERATOR) or partition granules (PX PARTITION [RANGE\|LIST\|HASH] ITERATOR or PX PARTITION [RANGE\|LIST\|HASH] ALL). The basic ideas surrounding these concepts are discussed in numerous blogs and books, including my...	10.1 parsecs away Travel
\|	\|	jonathanlewis.wordpress.com Plans in Memory \| Oracle Scratchpad	9.5 parsecs away Travel
\|	\|	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...	9.5 parsecs away Travel
\|	\|	nenadnoveljic.com Performance Improvement on Dictionary Views in Oracle 21c - All-round Database Topics	66.1 parsecs away Travel
\|		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.	66.1 parsecs away Travel