Data in a fact or dimenzion table or bridge table
2 posters
Page 1 of 1
Data in a fact or dimenzion table or bridge table
Hello
Please review how to create a model. I have health care providers belonging to several regional units.
Analysis will need to be varied according to regional units, as well as
which care providers belong to a regional unit
care providers Regional Unit
1000 1
1002 1
1002 2
Is it wise to have a regional unit in the FACT table as a foreign key (Regional Unit dimension) as well as in the table of Care providers.
Is it better to have fk of regional unit in dimension of providers and linked table of Regional unit and Care Providers.
Do I must have bridge table or j just put fk dimension of provider and i have relationship M:M in one table. With olap tool
I can define ralationships in one table.
Best regards and thanks in advance, K
Please review how to create a model. I have health care providers belonging to several regional units.
Analysis will need to be varied according to regional units, as well as
which care providers belong to a regional unit
care providers Regional Unit
1000 1
1002 1
1002 2
Is it wise to have a regional unit in the FACT table as a foreign key (Regional Unit dimension) as well as in the table of Care providers.
Is it better to have fk of regional unit in dimension of providers and linked table of Regional unit and Care Providers.
Do I must have bridge table or j just put fk dimension of provider and i have relationship M:M in one table. With olap tool
I can define ralationships in one table.
Best regards and thanks in advance, K
MK- Posts : 16
Join date : 2013-02-04
Location : Slovenia
Re: Data in a fact or dimenzion table or bridge table
Hi,
If you have Care Provider Key in your fact table, you cannot put the regional unit key of that record. Because that provider may belong to more than one Regional Unit.
I have seen some examples that identify one regional unit as "master", and put that "master key" in to the fact table.
But your case is the classical many to many problem and the solution is bridge table between your fact and Regional Unit dimension.
If you have Care Provider Key in your fact table, you cannot put the regional unit key of that record. Because that provider may belong to more than one Regional Unit.
I have seen some examples that identify one regional unit as "master", and put that "master key" in to the fact table.
But your case is the classical many to many problem and the solution is bridge table between your fact and Regional Unit dimension.
umutiscan- Posts : 51
Join date : 2010-11-26
Age : 44
Location : Istanbul, Turkey
Similar topics
» Design a snapshot Fact table in data mart from compliance-enable fact table in enterprise data warehouse
» How to resolve a many to many relationship? Bridge Table or Utilize the same fact table?
» separate fact table/different grain - do I need a bridge table
» Bridge Table - What is in the Fact tbl?
» difference between factless fact and bridge table
» How to resolve a many to many relationship? Bridge Table or Utilize the same fact table?
» separate fact table/different grain - do I need a bridge table
» Bridge Table - What is in the Fact tbl?
» difference between factless fact and bridge table
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum