I currently have a Claim Payment Fact Table that has on degenerative dimension for a "PaymentNumber"
The client now needs 3 additional non fact columns from the Operational Table that would also translate directly to the fact table based on where the data is sourced.
the new columsn are
1) Transcation Number
2) Payee Name
3) Journal Voucher Code
The cardinality is moderate so I was thinking of making a new dimesion and adding those three columns plus moving down payment into the new dimension.
Or am I better off having three more non fact columns in the fact table.
If I do make a new dimension, what would be considered the natural key from the Source ?
- Posts : 34
Join date : 2011-06-14
Create a separate dimension based on the transaction key. Most likely this table will only ever be used to get the detail on a small number of records in a drill through situation. If you put then in the fact table performance of other queries on that fact table would degrade for no good reason.
Permissions in this forum:You cannot reply to topics in this forum