handling cases in fact table
3 posters
Page 1 of 1
handling cases in fact table
Hello All,
I would like to know the best way and if possible automatic formula to handle the case : late arriving facts ?
Notice that I am not using an etl tool, only via stored procedure in pl/sql.
Thanks a lot for your help!
I would like to know the best way and if possible automatic formula to handle the case : late arriving facts ?
Notice that I am not using an etl tool, only via stored procedure in pl/sql.
Thanks a lot for your help!
NewDpr- Posts : 4
Join date : 2014-11-15
Re: handling cases in fact table
Usually the issue is late arriving dimensions. What is the issue with late arriving facts?
Re: handling cases in fact table
Yes, indeed the case is late arriving dimensions.
How this case can be solved with an SCD type 2 dim ?
How this case can be solved with an SCD type 2 dim ?
NewDpr- Posts : 4
Join date : 2014-11-15
Re: handling cases in fact table
Before you update your fact table, identify those business keys for which dimension rows do not yet exist, and create new dimension rows with each business key. When the dimension update arrives you can update the dimension table. Given that you've mentioned SCD2, you might want to think about special logic for the first update of a row that was created in this manner.
Similar topics
» Many cases for each Fact
» 'Routing' the grain of the fact table to multpile members of multiple dimensions causes the fact table to 'explode'
» Can a fact table be used as a source for populating another fact table
» How to create fact table with measures derived from comparing two fact table rows
» Healthcare Hospital Stay fact table - transaction fact table - a row for In and a row for Out?
» 'Routing' the grain of the fact table to multpile members of multiple dimensions causes the fact table to 'explode'
» Can a fact table be used as a source for populating another fact table
» How to create fact table with measures derived from comparing two fact table rows
» Healthcare Hospital Stay fact table - transaction fact table - a row for In and a row for Out?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum