Multiple fact tables or Calculated Measure
4 posters
Page 1 of 1
Multiple fact tables or Calculated Measure
Gurus,
This is my first question here...
We have loan application data with various statuses....
For example,Application with AppNo 1and stauts "logeed in" etc...(in logged-in data sheet))
similarly application with appno 1 and status "processig"...(in processing data sheet
we have until 5 status...
to the question..
Can we load all data in to single fact and create a calc measure or we need to create spearate table for all status....?
We need report like
How may application got logged in/processed/pending etc certain time period?
We are using SSIS/AS ...
Thanks in Advance
This is my first question here...
We have loan application data with various statuses....
For example,Application with AppNo 1and stauts "logeed in" etc...(in logged-in data sheet))
similarly application with appno 1 and status "processig"...(in processing data sheet
we have until 5 status...
to the question..
Can we load all data in to single fact and create a calc measure or we need to create spearate table for all status....?
We need report like
How may application got logged in/processed/pending etc certain time period?
We are using SSIS/AS ...
Thanks in Advance
saravanan.r- Posts : 4
Join date : 2011-04-27
Re: Multiple fact tables or Calculated Measure
There is no reason to create separate tables for each status.
Re: Multiple fact tables or Calculated Measure
Not required to create multiple fact tables. Either it can be a single fact table with one of the grain dimensions as 'Status' or store the computed measures based on the status against the loan application if there is defined set of measures against the status. The former would be preferable.
datamodeller- Posts : 9
Join date : 2010-07-25
Re: Multiple fact tables or Calculated Measure
You probably should use accumulating snapshot fact table based on Kimball’s methodology. In your case, you will have 5 date key fields as FKs of a single role playing date dimension to store all the application milestones. You then need to include any necessary time lag measures in your fact table and let ETL set the values when the relevant milestone has been reached. In this style of fact table, you would periodically revisit previous records and change date keys from nonexistence to a significant date accordingly.
hang- Posts : 528
Join date : 2010-05-07
Location : Brisbane, Australia
Similar topics
» Multiple Fact Table / Calculated Measure
» Calculated measure value in aggregate fact table
» Transaction fact table and Sql server analysis services calculated measure
» Modelling question - Multiple fact tables with one to many relationships and querying from many fact tables
» Joining Multiple Fact Tables
» Calculated measure value in aggregate fact table
» Transaction fact table and Sql server analysis services calculated measure
» Modelling question - Multiple fact tables with one to many relationships and querying from many fact tables
» Joining Multiple Fact Tables
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum