Why Oracle Physical I/Os are Expensive
Oracle physical I/O is about more than physical disks and I/O subsystem; it is also about the stuff that goes on inside when blocks are being read into the SGA.
Read MoreMost Popular
Why Change the Oracle DB_FILE_MULTIBLOCK_READ_COUNT?
A higher DB_FILE_MULTIBLOCK_READ_COUNT (MBRC) number can influence the Oracle optimizer to lean toward full table scans. Learn how this affects performance.
Read MoreWhy Do Oracle DB File Sequential Reads Show Up in a Full Table Scan?
There are four primary reasons why you see Oracle DB File Sequential Read wait events in a full scan operation. Learn more.
Read MoreMinimizing Oracle db file sequential Read Wait Events
To minimize the Oracle db file sequential read waits you can optimize the SQL statement or reduce the average wait time. Learn more.
Read MoreUnderstanding the Oracle db file sequential read Wait Event
The Oracle db file sequential read wait event is initiated by SQL statements that perform single-block read operations. Learn when these waits may indicate a need for tuning.
Read MoreWhy You Shouldn’t Rely on Oracle Trace Event 10046 for Performance Data Collection
While Oracle trace event 10046 is good for tracing processes,learn why it doesn’t meet the always-on and low overhead requirement necessary for continuous performance monitoring.
Read MoreWhy is Historical Oracle Performance Data Important?
DBAs are often blamed for problems unrelated to the database. This article makes the case that a DBA’s strongest defense is access to session-level historical performance data.
Read MoreUnderstanding the Oracle Library Cache Pin Wait Event
The Oracle library cache pin wait event occurs when the session tries to pin an object in the library cache to modify or examine it. Learn what actions to take to tune for it.
Read MoreDevOps–Collaborating to Improve Application Performance
In DevOps, IT development and IT database production must work together to build and improve application and database performance.
Read MoreThe Great Oracle Trigger Escape
Triggers are an often forgotten, yet critical, piece of code that can end up skewing an otherwise excellent design. Learn how this impacted one company’s performance.
Read MoreToo Many Indexes in SQL Server?
Too many SQL Server indexes create additional overhead associated with the extra amount of data pages that the Query Optimizer needs to go through.
Read MoreHow SQL Server 2012 Uses Indexes
The execution plan selected by the Query Optimizer may or may not make efficient use of indexes, or it may not use indexes at all. The following sections describe how execution plans can use indexes.
Read More