How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)

J.Moelands Sun May 09, 2010 9:37 am

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 manage the type I and / or type II mutations within this construction. Are there any limitations to this constructions (for example in the snowflake sub dimension there cannot be any type II fields etc..)
In which sequence will the data arrive in the dimension (sub) tables, first load the customer dimension and the insert all the records based on the sub snowflake key within the snowflake sub dimension? There is not much information on how to ETL this kind of constructions.

Hope the writers of the book can clear this out for me :-)
Thanks in advantage!

Regards
Joey Moelands.