Vehicle Operations
3 posters
Page 1 of 1
Vehicle Operations
Hi
I have a Vehicle Dimension table that contains the VIN, Purchase date, Manufactured Date, Make , Model and a few other attributes
I also wat to create a VehicleOperations snapshot fact table that contains Vehicle Age, Odometer Reading and a few other attributes. Do you think it is worth putting in the fact table date keys for the Purchase Date & Manufactured Date ?
Regards
Tim
I have a Vehicle Dimension table that contains the VIN, Purchase date, Manufactured Date, Make , Model and a few other attributes
I also wat to create a VehicleOperations snapshot fact table that contains Vehicle Age, Odometer Reading and a few other attributes. Do you think it is worth putting in the fact table date keys for the Purchase Date & Manufactured Date ?
Regards
Tim
tim_goodsell- Posts : 49
Join date : 2010-09-21
Re: Vehicle Operations
I assume your design is based on your business' requirements so your business users will be able to provide you with the answer to these questions: if they want to report on these date attributes then you need them in the fact table and if they don't then you don't
nick_white- Posts : 364
Join date : 2014-01-06
Location : London
Re: Vehicle Operations
Assuming the Purchase Date and Manufactured Date do not normally change across the life of a Vehicles Dimension row, then I would not include them in a Snapshot Fact - they would be redundant and could be easily retrieved from the Dimension. Even if you did need to track changes I would go with a Type 2 SCD design in the dimension rather than put them in the Snapshot Fact
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|