BC remote Oracle DBA - Call (800) 766-1884  
Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation









Pre-calculating and Storing Summary Data

Oracle Tips by Burleson Consulting

The Data Warehouse Development Life Cycle

Aggregating Data For The Oracle Warehouse A Method For Pre-calculating And Storing Summary Data

If we are using a vanilla Oracle database without a multidimensional engine, we can create a method for determining new tables that will contain summary data. Then, we can come up with a method for keeping these summary tables correct. Letís start by examining the table structure of our existing data warehouse. As you saw in Figure 6.3, the fact table is highly de-normalized and there are two facts: quantity_sold and total_cost. (the facts are usually listed last in the fact table, after all of the key columns) You also saw that there are dimensions of attributes relating to customers, salespersons, and items. Now, letís take a look at how we might create aggregate tables from this model.

Determining The Number Of Aggregate Tables

The first step in creating summary data tables is to identify all the possible dimensions that our Oracle warehouse will use. Letís start by listing the dimension attributes that might be used in our summary tables, such as:

* Month

* Quarter

* Year

* Customer_name

* Customer_city

* Customer_state

* Customer_region

* Item_name

* Item_Price

* Salesperson_name

This is an excerpt from "High Performance Data Warehousing".

If you like Oracle tuning, you may enjoy the book Oracle Tuning: The Definitive Reference , with over 900 pages of BC's favorite tuning tips & scripts. 

You can buy it directly from the publisher and save 30%, and get instant access to the code depot of Oracle tuning scripts.


Expert Remote DBA

BC is America's oldest and largest Remote DBA Oracle support provider.  Get real Remote DBA experts, call
BC Remote DBA today.



Remote DBA Service

Oracle Tuning Book


Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software







BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracleģ is the registered trademark of Oracle Corporation.