Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 04 May 2004 @ 18:49:54 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: EDW - Logically Integrated across multiple DBs v/s Single DB
 
From:   Rajiv-Devulapalli

Interesting articles by Michael and Edmond.

The places where I have worked on Teradata have a data model very similar to what is described by Edmond.

There was a separate subject area by database, and a common dimension database, which is used to tie them all together.

Generally, from my experience, each subject area has a different ETL load cycle, different backup requirements and different, independent and sometimes conflicting reporting requirements ( even for similar dimensions). For example, in retail industry, there are several different "calendars" used to report sales/end of period inventory --> a single time dimension will not suffice in that case. Having all subject areas in a single database tends to make that database unmanageable and cluttered.

What we were thinking was to create a view database - that would point to all the subject area databases, thereby providing "end-users" a single access-point to enterprise data across all subject areas - without the underlying tables all having to live together.

Maybe it is just a matter of how "enterprise" the EDW really is !!!



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 23 Jun 2019