The initialization parameter OPTIMIZER_INDEX_COST_ADJ has a certain popularity in the area of Oracle Database Performance Tuning. Especially, it can be used to make the Optimizer favor index access instead of full table scans. But that is not necessarily appropriate – in fact it can have very counterproductive effects on performance. Richard Foote has some very instructive postings about this, especially this one is impressive, in my view.
When is setting OPTIMIZER_INDEX_COST_ADJ appropriate?
- Like uhesse.com on Facebook
I’m speaking
Blog Follower
Recent Comments
Daren on Speed up Import with TRANSFORM… oraclenerd on Adding Tablespaces/Datafiles w… Saeed on Dealing with Oracle Database B… Saeed on Dealing with Oracle Database B… Mark Miller on Transport Tablespace using RMA… VIJAY HINDURAO SHITO… on Exadata Quarter Rack Architect… How do Nologging Ope… on How do NOLOGGING operations af… ynixon on Connect Time Failover & Tr… ynixon on Use RMAN to create your standb… Grzegorz Goryszewski on Combining Resource Consumer Gr… Peter on adrci: A survival guide for th… Peter on adrci: A survival guide for th… 
#1 by bernardino on August 26, 2014 - 23:26
buenas articulos
#2 by Nassou on August 23, 2016 - 17:20
I agree, and especially perfectly detailed and explained with consistency.