One Fact Table or Two

View previous topic View next topic Go down

One Fact Table or Two

Post  KKumar on Sun Apr 12, 2015 11:47 am

I am working on a star schema for a construction project model. We have 2 groups of users- one who wants to see only approved projects and the other group want to see project (approved and unapproved).

One option was to build 2 facts, one only with approved and other one with all the project. But this option will increase ETL Maintenance and increase db storage.

Second option was to create one fact table with all the projects and adding an indicator to the fact (Approved or Unapproved) and then creating a view that filters only approved projects for the first group of users. This option is less load on ETL but not sure if keeping indicators in fact is good idea.

Not sure if there is any other option.

Please advise.

Thanks




KKumar

Posts : 22
Join date : 2011-07-29

View user profile

Back to top Go down

RE: One Fact Table or Two

Post  hkandpal on Mon Apr 13, 2015 8:47 am

you should try the 2nd option, keeping the indicator in your fact. You can store the indicator in a junk dimension. If tomorrow you decide to have stage other than approved and unapproved for a project then this way you don't have to change the ETL code.


thanks

hkandpal

Posts : 113
Join date : 2010-08-16

View user profile

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum