person_employee dimension
2 posters
Page 1 of 1
person_employee dimension
i have a dimension as person_employee, i want to have them as separate dimension for my model is that a good idea?
with person all the information about that particular person will be included where as in employee all the information about the employee, related to the employer, will be included. Is this ok to do or should i leave them as one dimension
with person all the information about that particular person will be included where as in employee all the information about the employee, related to the employer, will be included. Is this ok to do or should i leave them as one dimension
varun- Posts : 5
Join date : 2011-09-28
Re: person_employee dimension
If there's no business reason to support Party type consolidation, I would leave as separate entities. This is especially true if you are not using a data quality tool to manage the consolidation.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Similar topics
» Replacing Aggregate dimension with Conformed base dimension at lowest level.
» How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)
» bridge table and junk dimension on customer dimension (bank/credit union)
» Modeling an Employee Dimension to a Fact which has two columns relating to the Dimension
» Using the Date Dimension for Summary Fact Tables or new specialized Month Dimension?
» How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)
» bridge table and junk dimension on customer dimension (bank/credit union)
» Modeling an Employee Dimension to a Fact which has two columns relating to the Dimension
» Using the Date Dimension for Summary Fact Tables or new specialized Month Dimension?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|