meb97me at 16h58
25
Aug
2010
Handling "Unknown" Dimension atrributes that are Type 2 changes
In the data warehouse we're building, we've got an Employee dimension that has a self referencing attribute called ReportsTo which stores the surrogate key of their line manager who is also in the DW (in most cases). This attribute is a type 2 change as we want to capture historical heirachical changes in the company, however some people aren't always assigned a valid manager (its a really crappy system that i w
In the data warehouse we're building, we've got an Employee dimension that has a self referencing attribute called ReportsTo which stores the surrogate key of their line manager who is also in the DW (in most cases). This attribute is a type 2 change as we want to capture historical heirachical changes in the company, however some people aren't always assigned a valid manager (its a really crappy system that i w
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
Hi. I'm trying to find a good way to handle late changes to Type 2 attributes. Please note that I am not asking about early-arriving facts that could be handled with an inferred dimension member. Rather, I am interested in the situation where the dimensio
Hi,
I'm in the process of designing a dimensional model for a product warehouse, and a question I have is about how to handle a change of a Type 2 dimension in a related fact. I am keeping the details of each of our products in a Type 2 dimension (name
Can anyone explain in detail on what is the rationale behind having the dimension start with Type 0 and also for the missing type 5
I am trying to find a best example / scenario where a type 3 scd would make more sense than a type 2. In my understanding type 3 can easily be derived from type 2.
If anybody has used type 3 dimension instead of type 2, please let me know the scenario an
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
Forums from same category
HmongThoobNtiajTeb. com/
Free forum : hi. Free forum : 2709rsgamboa6219. Free forum,
Free forum : Forum IT Teknik Komputer dan Jaringan SMKN 1 SLAWI
LEGO Island Discussion, modding, news and more!
Techy Boards, a growing technology discussion forum! For fans of nintendo, xbox, playstation or anything else!
Search
Informations
2 Replies For the topic :
"Handling "Unknown" Dimension atrributes that are Type 2 changes"
This topic has been viewed 1129 times.
Last message :
25/08/2010 at 16h58 by "meb97me"






