How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)
J.Moelands at 15h37
09
May
2010
How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)
Hello,
Within Ralph his new book he describes recommanded situations for snowflaking a dimension. His example is a large customer (visitor) dimension. (page 337, 338 and figure 10-6). I find the artical good, but there is missing one part of this solution -> how to implement this within the ETL boundaries described by kimball.
Im very interested how to
Hello,
Within Ralph his new book he describes recommanded situations for snowflaking a dimension. His example is a large customer (visitor) dimension. (page 337, 338 and figure 10-6). I find the artical good, but there is missing one part of this solution -> how to implement this within the ETL boundaries described by kimball.
Im very interested how to
About
This topic belongs to the forum
Data Warehousing and Business Intelligence based on dimensional modeling and the Kimball Lifecycle.
- Numbers of topics : 1858
- Numbers of messages : 8714
- Numbers of users : 3801
- Numbers of points : 1672
Similar topics
As part of an Orders dimensional model, I am attempting to design the Customer Dimension table. The customers have multiple sold-to addresses and multiple ship-to addresses. While the OLTP allows any Order to have any combination of sold-to and ship-to
I am trying to model a Customer Dimension with Educational and Employment details and I want some advice on how to model this scenario
A Customer can have several levels of Education like schooling, college, university, training (one to many realtionship
I am designing a dimensional model for employee data in a data warehouse. Right now I only register the basic information about the employee, like job title, department, language, FTE, etc. I have chosen to use an SCD Type 2 dimension since I want to keep
We're using Oracle and I received the following (see below) from our architect about why we shouldn't create a new SK for every type 2 change. i.e. use a combination of date and sk as the primary key.
Is this correct. Will it affect the creation of
Im currently attempting to define a customer dimension that has a fixed set of fields as well as an unlimited number of user-defined fields. The user-defined fields can be of various data types defined by the user. For example, a user may define a fiel
Forums from same category
LEGO Island Discussion, modding, news and more!
Free forum : Forum IT Teknik Komputer dan Jaringan SMKN 1 SLAWI
Techy Boards, a growing technology discussion forum! For fans of nintendo, xbox, playstation or anything else!
Free forum : hi. Free forum : 2709rsgamboa6219. Free forum,
HmongThoobNtiajTeb. com/
Search
Informations
0 Replies For the topic :
"How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)"
This topic has been viewed 1139 times.
Last message :
09/05/2010 at 15h37 by "J.Moelands"





