Explore >> Select a destination

You are here

 danischnider.wordpress.com
Star Schema Optimization in Autonomous Data Warehouse Cloud | Data Warehousing with Oracle
| | dincosman.com
Direct Path Read Decision in Oracle: Beyond the Optimizer - Osman's DBlog
2.6 parsecs away

Travel
| | The performance issue with an SQL query was resolved by using the /*+ PARALLEL(2) */ hint, reducing execution time from 180-200 seconds to milliseconds. The decision to perform a direct read from disk to memory instead of reading blocks from disk was made by the database engine and is controlled by the hidden "_serial_direct_read" parameter....
| | tonyhasler.wordpress.com
Parallel partition scans | Tony's Oracle Tips
3.0 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...
| | rwijk.blogspot.com
About Oracle: dbms_xplan.display_cursor
3.3 parsecs away

Travel
| |
| | jonathanlewis.wordpress.com
Bind Peeking | Oracle Scratchpad
23.0 parsecs away

Travel
| Here's a simple detail about bind peeking (during optimisation) that makes a big difference to "fetch first/next" queries. The optimizer knows about your bind types, and can peek at the bind values - but that doesn't mean it will do something sensible with them. Here's a little model to demonstrate the problem - starting with...