Home
Kimball Group Home
Search
Register
Log inTransaction level granularity
2 posters
Page 1 of 1
Transaction level granularity
sirmhb Tue Nov 12, 2013 8:48 am
Hi
I have a fact table which it contains transaction information like "Transaction Amount" ,"Transaction date and time" , "Transaction ID" and etc
"Transaction ID" is primary key of fact table.I need transaction level granularity.
Can I use Fact table Primary key ("Transaction ID") as a Dimension?
If not how should I design my data warehouse so I can have transaction level granularity?
Regards
I have a fact table which it contains transaction information like "Transaction Amount" ,"Transaction date and time" , "Transaction ID" and etc
"Transaction ID" is primary key of fact table.I need transaction level granularity.
Can I use Fact table Primary key ("Transaction ID") as a Dimension?
If not how should I design my data warehouse so I can have transaction level granularity?
Regards
sirmhb- Posts : 1
Join date : 2013-11-12
Re: Transaction level granularity
ngalemmo Tue Nov 12, 2013 11:53 am
Transaction ID can be a degenerate dimension value in a fact table.
ngalemmo- Posts : 3000
Join date : 2009-05-15
Location : Los Angeles -
Similar topics» Coupons At the Order level not the Product Level
» Transaction with Multi level Hierarchy
» how to handle mutiple level granularity in retail domain dimensional model
» Transaction fact without obvious transaction type field
» Multiple transaction types, Average Transaction Value, and KPIs
» Transaction with Multi level Hierarchy
» how to handle mutiple level granularity in retail domain dimensional model
» Transaction fact without obvious transaction type field
» Multiple transaction types, Average Transaction Value, and KPIs
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum