NULL Values in Fact Table
2 posters
Page 1 of 1
NULL Values in Fact Table
In an Accumulating Snapshot that has multiple dates, where we are revisiting the fact rows as additional events occur, should the foreign keys to the date dimension for dates that have not yet occurred be set to NULL or should they point to a "dummy" row in the date dimension.
Thanks
Thanks
jimbo1580- Posts : 23
Join date : 2009-04-30
Re: NULL Values in Fact Table
Reference to an inferred (dummy) row in the Dim table is always preferred. Following are some of the reasons:
1. The where clause in the queries on the fact table doesn't need to consider null different from other values ("IS NULL" vs. "= Value").
2. The absence of a late arriving dimension value may be for multiple reasons and you can have one inferred (dummy) row in the Dim table for each of these reasons. These reasons will be visible in your reports based on what attribute values you store for the inferred row.
1. The where clause in the queries on the fact table doesn't need to consider null different from other values ("IS NULL" vs. "= Value").
2. The absence of a late arriving dimension value may be for multiple reasons and you can have one inferred (dummy) row in the Dim table for each of these reasons. These reasons will be visible in your reports based on what attribute values you store for the inferred row.
amarpal- Posts : 3
Join date : 2010-01-14
Similar topics
» Lab Result values in Fact Table has int and non int values
» How to handle date field with a null value in the fact table ?
» Factless fact table with null foreign keys
» Dummy dimension values in the fact table
» How to Handle a value in a fact table that can have multiple dimension values
» How to handle date field with a null value in the fact table ?
» Factless fact table with null foreign keys
» Dummy dimension values in the fact table
» How to Handle a value in a fact table that can have multiple dimension values
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum