Customer Both as Fact and Dimension
2 posters
Page 1 of 1
Customer Both as Fact and Dimension
In our business, our customers are subscribers so they can be active or inactive status.
Part of the reporting requirements is to show how many subscribers there are based on when they joined.
So is it best to do this via a Factless Fact table?
E.g.,
FACTCUSTOMERS
- FACTCUSTKEY (PK)
- CUSTKEY (FK)
- JOINDATE_KEY (FK)
DIMCUSTOMERS
- CUSTKEY (PK)
- RECORD_STATUS (SCD)
- STARTDT (SCD)
- ENDDT (SCD)
Is this the right way to do this?
Thanks
Part of the reporting requirements is to show how many subscribers there are based on when they joined.
So is it best to do this via a Factless Fact table?
E.g.,
FACTCUSTOMERS
- FACTCUSTKEY (PK)
- CUSTKEY (FK)
- JOINDATE_KEY (FK)
DIMCUSTOMERS
- CUSTKEY (PK)
- RECORD_STATUS (SCD)
- STARTDT (SCD)
- ENDDT (SCD)
Is this the right way to do this?
Thanks
ohmycamote- Posts : 14
Join date : 2011-07-05
Re: Customer Both as Fact and Dimension
Customer is a dimension, never a fact. The fact in question is subscription, not customer. You would have a subscription fact table of which customer is one of the dimensions.
Similar topics
» Add customer attributes to fact or new dimension
» Connecting Actual and Budget Fact table to same Product and Customer Dimension
» Merging customer data from disparate sources to create a master customer dimension
» Work Order / Customer Order Design - Dimension or Fact
» De-normalizing Customer Information to create a Customer Dimension
» Connecting Actual and Budget Fact table to same Product and Customer Dimension
» Merging customer data from disparate sources to create a master customer dimension
» Work Order / Customer Order Design - Dimension or Fact
» De-normalizing Customer Information to create a Customer Dimension
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|