Modeling a Product Dimension
3 posters
Page 1 of 1
Modeling a Product Dimension
Hello All,
Wanted to reach out to you to exchange few thoughts on how to model a product dimension with the below details:
The product dim entity has columns like : Product_name, Product_Id, Expiry Period and so on....
The expiry period keeps changing. Let us say, today it is going to expire within 100 days. Tomorrow, it will be 99 days.
The source owners keeps sending the product data daily with the changes. One change would be for sure in the expiry period column.
I am supposed to model it as a Type 2 dimension. However, without 2 rows (example, old row for 100 days/new for 99 days) getting created daily in my dimension table. I mean, any other means of taking this 'expiry period' data out of this table?
Any thoughts on how to model this situation? Appreciate the help!!!
Kind Regards,
Noor.
Wanted to reach out to you to exchange few thoughts on how to model a product dimension with the below details:
The product dim entity has columns like : Product_name, Product_Id, Expiry Period and so on....
The expiry period keeps changing. Let us say, today it is going to expire within 100 days. Tomorrow, it will be 99 days.
The source owners keeps sending the product data daily with the changes. One change would be for sure in the expiry period column.
I am supposed to model it as a Type 2 dimension. However, without 2 rows (example, old row for 100 days/new for 99 days) getting created daily in my dimension table. I mean, any other means of taking this 'expiry period' data out of this table?
Any thoughts on how to model this situation? Appreciate the help!!!
Kind Regards,
Noor.
noor_infa- Posts : 1
Join date : 2012-07-25
Re: Modeling a Product Dimension
Just because a dimension is Type-2 doesn't mean that every attribute needs to be tracked historically.
Treat the expiry period attribute as a type-1 attribute, and exclude it from your type-2 logic.
Treat the expiry period attribute as a type-1 attribute, and exclude it from your type-2 logic.
LAndrews- Posts : 132
Join date : 2010-05-13
Location : British Columbia, Canada
Re: Modeling a Product Dimension
Or would it not make sense to store it as a date? For example, if the source contains a value of 50 and you know it means 50 days from today, just do the math and calculate what that date is and store the date in the dimension. The date will change far less often than number of days remaining. In reporting you can always do a calculation to revert it back to the number of days. Its basically the same issue as storing birthdate instead of age.
Similar topics
» Product Dimension Question
» Dimensional modeling of product and vendor for invoice fact
» Product Portfolio Dimension
» Product dimension with many options?
» Populating Product dimension
» Dimensional modeling of product and vendor for invoice fact
» Product Portfolio Dimension
» Product dimension with many options?
» Populating Product dimension
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum