Dimensional Model Tips

View previous topic View next topic Go down

Dimensional Model Tips

Post  RM7 on Thu Jun 13, 2013 12:12 pm

Hi

We are trying to implement Dimensional Modelling for the report requirement for the user group. The overall source system can be represented as:


I have transactional information / measures available for different services and there are different attributes available for each service and the same applies to Orders, Privileges, Publishes & Reviews. Do we need to have fact table for each service and each for order or to create one big fact at the lowest grain available?†

We are building this to accommodate Operational reporting. So I canít aggregate any information and need to bring in the same grain of information that is available in source.

Any suggestions would be appreciated.


Thanks
RM

RM7

Posts : 3
Join date : 2012-10-10

View user profile

Back to top Go down

RE: Dimensional Model Tips

Post  rathjeevesh on Sun Jun 16, 2013 4:53 pm

For operational reporting I would suggest not to go for star schema. You can adopt a denormalized version (optimized for reporting) of ER model and bring the concept of generalization and specialization for data storage, based upon what you have shared regarding the source data.

-JR

rathjeevesh

Posts : 15
Join date : 2013-02-16

View user profile

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum