[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference heron::dw_tools

Title:Datamart & Datawarehouse tools support
Moderator:HERON::ROWLANDS
Created:Thu Nov 28 1996
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:45
Total number of notes:155

30.0. "Datamart Vs Data Warehouse" by HERON::ROWLANDS (Rob Rowlands @vbo 828 5480) Fri Mar 21 1997 15:51

You'll find in the usual directory:

heron::pub_dsk:[public.datamart_service]

dmart_vs_dware.ppt 

a scripted presentation on Datamarts vs Data Warehouse.

It's important that we can all discuss this openly with customers and
prove to them that building multiple datamarts does NOT lead to data havoc. The
presentation describes how one can ensure that well-designed datamarts can grow
into data warehouses maintaining data coherency throughout the process.

Happy hunting!
T.RTitleUserPersonal
Name
DateLines
30.1Architecture is THE solutionIJSAPL::OLTHOFSpellchecked Henry AlthoughFri Mar 21 1997 16:4130
    Well,
    
    The presentation mentions the problem and the way it should be solved.
    The way is to look for common dimensions, or generic dimensions like
    they are called in the Solution Architecting Data Warehouses workshop.
    Ralph Kimball uses the same terms in his excellent class on data
    modeling for the Data Warehouse. He even says it a bit stronger: the
    Data Warehouse is a conglomerate or cluster of individual Data Marts,
    tied together by common dimensions.
    
    Question remains: how do you develop these generic dimensions in order
    to have scaling. The answer is that you need some architectural
    blueprint to achieve that, where common dimensions are discovered when
    developing the technical view (subject area's overview model). This
    model is (and should be) closely linked to the value chain of the
    organization. In the workshop mentioned above this process is tought.
    
    The problem as described in the presentation is very real. I just
    returned from a visit at a large company in Israel where this problem
    manifested itself. The customer saw no escape besides:
    - delaying, possible stalling the current implementation of a DM in one
      of the departments, caused others jumping on the wagon
    - developing seperate DM's, with great chance of leading to islands of
      data
    Digital offered help by doing a short (say 3 days) architecture
    workshop in parallel to re-synchronise and discover generic dimensions.
    We are in the unique position to be able to do this.
    
    Cheers,
    Henny
30.2Conceptual designULYSSE::BAUDELLEMon Mar 24 1997 09:5822
    
    	Henny,
    
    	You are exactly right and in the Rams training for Data marts we
    have just extended with a design part we are trying to address this step.
    	What is built in front of the Logical (star-schema in this case) is
    a conceptual design where the business view (also called subject
    data-model) is described. The intent of this high-level modelling is to
    catch the common dimensions, model the output view and check it against the
    data sources to make the project safe (especially for a 6 weeks
    project : early in the process). Ralph Kimball told me that he usually
    spends 5-6 weeks on it for a full Data-warehouse at the beginning of
    the process: for the Ddm we are only focusing on one subject-area.
    
    The next DataMart will be consolidated with the first one built (to
    share the common dimensions) and even a migration to a Datawarehouse would 
     re-use this conceptual design.
    
    
    Cheers
    
    Pierre