I request an opinion on a modeling problem
3 posters
Page 1 of 1
I request an opinion on a modeling problem
I've got three objects.
1. Parent Company
2. Subsidiary
3. User
I collapsed the parent/subsidiary into one dimension. I'm not sure what to do with user. A user can belong to a parent, a subsidiary, or both. I thought about snowflaking the User dimension and just putting in flags to indicate were the user belonged. Thoughts?
1. Parent Company
2. Subsidiary
3. User
I collapsed the parent/subsidiary into one dimension. I'm not sure what to do with user. A user can belong to a parent, a subsidiary, or both. I thought about snowflaking the User dimension and just putting in flags to indicate were the user belonged. Thoughts?
falcon00- Posts : 17
Join date : 2013-11-07
Re: I request an opinion on a modeling problem
Its a business state. It is handled with a fact table that contains user & parent/subsidiary as dimensions.
Re: I request an opinion on a modeling problem
See I thought this looked like a factless fact table but I'm not quite certain I'm following. How exactly would you indicate that a user might belong to just one entity in the company hierarchy? I may have my parent/subsidiary table not modeled properly.
dim_user(user_ck PK)
dim_business(business_ck PK, parent, subsidiary)
now the fact table looks like:
fact_user_employer(user_ck FK, business_ck FK)
In this case I can only see that a user belongs to both. What am I missing?
dim_user(user_ck PK)
dim_business(business_ck PK, parent, subsidiary)
now the fact table looks like:
fact_user_employer(user_ck FK, business_ck FK)
In this case I can only see that a user belongs to both. What am I missing?
falcon00- Posts : 17
Join date : 2013-11-07
Re: I request an opinion on a modeling problem
Create a row where the Parent Company is also the subsidiary. Might change the name a little to show the Parent Company in this instance only contains users with direct relationships.
Jeff Smith- Posts : 471
Join date : 2009-02-03
Similar topics
» Concrete problem modeling new requirement (increasing one dimension). Help needed! :)
» The age problem
» Too many dates on fact - Is there such a thing as Junk Date dimension
» data model for 2 fact tables (Header / Detail scenario)
» Request and Workflow Process
» The age problem
» Too many dates on fact - Is there such a thing as Junk Date dimension
» data model for 2 fact tables (Header / Detail scenario)
» Request and Workflow Process
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum