Why Oracle 10g for the Data Warehouse?
The large data buffer caches in most OLTP Oracle systems make them CPU-bound, but Oracle data warehouses are another story. With terabytes of information to aggregate and summarize, most Oracle data warehouses are I/O-bound, and you must choose a server that optimizes disk I/O throughput. Oracle has always made very large database (VLDB) technology a priority as evidenced by their introduction of partitioned structures, advanced bitmap indexing, and materialized views. Oracle10g provides some features that are ideal for the data warehouse application. You can easily see when an Oracle warehouse is disk I/O bound. In the following AWR report (STATSPACK report for Oracle9i and earlier), you can see a typical data warehouse system that is clearly constrained by disk I/O, resulting from the high percentage of full-table and full-index scans. A STATSPACK (AWR) Top 5 Timed Event Report for an I/O-bound Server Here you can see that scattered reads (full-table scans) constitute the majority of
