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

 

 


 

 

 

 

 

 
 

Oracle Tips 

by Burleson Consulting

The Data Warehouse Development Life Cycle

AD HOC CLASSIFICATION

One common mistake in data warehouse analysis is the failure to plan for new classifications of data warehouse attributes. These classifications are not always known in advance, and it is not uncommon to see that the delivery of the data warehouse provides end users with a mechanism for identifying new classifications.

In our example for Guttbaum’s Grocery, we might see arbitrary, or ad hoc, groupings of data attributes. These ad hoc groupings of existing data attributes might be used to perform what-if analyses for decision support. Some examples of ad hoc classification might include:

* A “yuppie” (young urban professional)--This is an individual in age category two or three, with an income greater than $50,000 a year, who owns his or her home and has less than four children. Show me a breakdown by product category for all yuppie expenditures on non-food items.

* A “dink” (dual-income, no-kids)--This is a family unit where there are two wage earners with a combined yearly income greater than $60,000. Show me the buying habits of dinks for dairy products.

* A “cheapskate”--This is an individual who uses coupons for more than 50 percent of their purchases. Show me the buying habits of cheapskates for all non-coupon purchases.
As you can see, the ability of the data warehouse to develop arbitrary classifications can greatly improve the usefulness of a data warehouse. Note that these classifications do not always form a hierarchy, and that they may sometimes be required for the pre-calculation of aggregate values. For example, we may need our data warehouse to pre-summarize sales by product classes and brands for yuppies, dinks, and cheapskates.


This is an excerpt from "High Performance Data Warehousing". To learn more about Oracle, try "Oracle Tuning: The Definitive Reference", by Donald K. Burleson.  You can buy it direct from the publisher at 30% off here:
http://www.rampant-books.com/book_1002_oracle_tuning_definitive_reference_2nd_ed.htm
 

 


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.