Bisquite at 16h44
07
Feb
2010
Preserving prior history for late arriving dimensions
Can't find much about this topic anywhere else so hopefully someone can help me.
Our warehouse has late arriving dimensions for an Employee. Their department changes, for example, can be backdated in the systems and so we have to account for this and adjust the effective dates in the SCD and the relevant surrogate keys in the affected sales fact table.
This is covered nicely in the "Data Warehouse Toolkit
Can't find much about this topic anywhere else so hopefully someone can help me.
Our warehouse has late arriving dimensions for an Employee. Their department changes, for example, can be backdated in the systems and so we have to account for this and adjust the effective dates in the SCD and the relevant surrogate keys in the affected sales fact table.
This is covered nicely in the "Data Warehouse Toolkit
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
Hello All,
Need some inputs regarding handling of late arriving facts:
I have a demographics related fact table that holds the following measures - Population_Count, Birth_Count, Death Count.
The behaviour of the Population_Count is that it stores
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
I am loading a Star Schema from a data base that acts as the staging area. We are converting our source systems to a new transaction system. We are converting data to the new transaction systems in large chunks with conversion dates spread over 3 years.
It is a data warehouse optimization project and a very basic data warehouse is in place. There are a couple of dimensions with only 2, 3 columns only (<30 rows) and where the Business key can be easily interpreted.
Ex: Event_Type_DIM: this has 2
I currently working on an Accounting Datamart which the dims and facts are loaded daily. I have recently had a request to update the data after its been loaded. The best way for me to explain this is to give an example.
The data is loaded daily, so
Forums from same category
Techy Boards, a growing technology discussion forum! For fans of nintendo, xbox, playstation or anything else!
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!
HmongThoobNtiajTeb. com/
Search
Informations
7 Replies For the topic :
"Preserving prior history for late arriving dimensions"
This topic has been viewed 2778 times.
Last message :
07/02/2010 at 16h44 by "Bisquite"






