Null Foreign Key
Page 1 of 1 • Share •
Null Foreign Key
So is this an exceptable practice in the Data Warehouse?
I have a situation where an employee is terminated and the reporting relationships no longer exists.
I have a situation where an employee is terminated and the reporting relationships no longer exists.
kkraemer- Posts: 2
Join date: 2009-02-03
Location: Chicago
Re: Null Foreign Key
The relationship existed when the fact row was created. Do you want to alter history?

BoxesAndLines- Posts: 562
Join date: 2009-02-03
Location: USA
Re: Null Foreign Key
There is no requirement to maintain historic reporting relationships
kkraemer- Posts: 2
Join date: 2009-02-03
Location: Chicago
Re: Null Foreign Key
The I offer that you do not need a data warehouse.

BoxesAndLines- Posts: 562
Join date: 2009-02-03
Location: USA
Re: Null Foreign Key
I'm not familiar with your warehouse but to me this sounds like it could be solved pretty easily by flagging your employee dimension record. The simplest solution being an 'active' boolean flag. That could be filtered at the report level to exclude anyone not currently active (termed). It could also be a term date that gets filtered out on the report.
I'd need more requirements in order to design something more elegant.
I'd need more requirements in order to design something more elegant.

BrianJarrett- Posts: 61
Join date: 2009-02-03
Age: 37
Location: St. Louis, MO
Similar topics» Null Foreign Key
» Factless fact table with null foreign keys
» Best Praticte for inserting fact and linking to dimensions
» Null values in facts, yes or no?
» null values best practice digest
» Factless fact table with null foreign keys
» Best Praticte for inserting fact and linking to dimensions
» Null values in facts, yes or no?
» null values best practice digest
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum