transactional fact vs periodic snapshot fact
4 posters
Page 1 of 1
transactional fact vs periodic snapshot fact
What is the difference between transactional fact and periodic snapshot fact table? As per my knowledge transactional fact table store each record per transaction and its short lived where as periodic fact table also does the same thing. I could not understand the diff between these two fact tables. Can some one please explain me? Thanks
rammnch- Posts : 5
Join date : 2013-10-10
Re: transactional fact vs periodic snapshot fact
A transactional fact is one where the rows represent a net change. For example, a bank transaction where you deposit $10. The measure in the fact is $10, which represents a net change to your balance. Transactional facts are typically insert only.
Snapshot facts represent a state, a periodic snapshot is one that represents states over time. For example, my bank balance right now is $500. A fact table that contains my current balance is a snapshot fact. (Note, a transactional fact that contains a running balance measure is still considered transactional). A periodic snapshot may contain my balances at the end of each month over some period of time. Snapshots may be updated in place.
A fact table containing sales order lines may be one or the other depending on how it is designed. If you just store the order line, and when it is changed, the line is updated, its a snapshot. If you store a new complete image of the lines when it is changed, it is an accumulating snapshot. If you store the difference between the original line and the new line (i.e. net change), it is transactional.
Neither type has anything to do with the retention of the data. A transactional fact is by no means 'short lived'.
Snapshot facts represent a state, a periodic snapshot is one that represents states over time. For example, my bank balance right now is $500. A fact table that contains my current balance is a snapshot fact. (Note, a transactional fact that contains a running balance measure is still considered transactional). A periodic snapshot may contain my balances at the end of each month over some period of time. Snapshots may be updated in place.
A fact table containing sales order lines may be one or the other depending on how it is designed. If you just store the order line, and when it is changed, the line is updated, its a snapshot. If you store a new complete image of the lines when it is changed, it is an accumulating snapshot. If you store the difference between the original line and the new line (i.e. net change), it is transactional.
Neither type has anything to do with the retention of the data. A transactional fact is by no means 'short lived'.
Re: transactional fact vs periodic snapshot fact
What would you call a fact table built from Loan Application system?
What if you wanted to see Load Applications that were fully adjudicated (denied, approved) as well as a count of records in the various stages of being processed? A person managing Loan Products may want to see the Denial Rate and a person managing the load processing group might want to see how many applications are being processed per day, the number of applications that are in middle of being processed, number of applications that have been in the system for more than 1 day, 2 days, 15 days, etc.
Would you have 1 transaction table and update the status of the application or would you have 2 facts, one with completed applications and the other with multiple versions of the application (a version for each change in status)?
What if you wanted to see Load Applications that were fully adjudicated (denied, approved) as well as a count of records in the various stages of being processed? A person managing Loan Products may want to see the Denial Rate and a person managing the load processing group might want to see how many applications are being processed per day, the number of applications that are in middle of being processed, number of applications that have been in the system for more than 1 day, 2 days, 15 days, etc.
Would you have 1 transaction table and update the status of the application or would you have 2 facts, one with completed applications and the other with multiple versions of the application (a version for each change in status)?
Jeff Smith- Posts : 471
Join date : 2009-02-03
Re: transactional fact vs periodic snapshot fact
If the fact represents an image of what the complete state of the transaction was at a point in time, it is a snapshot. Wither you update in place or maintain versions of it over time, it is still a snapshot. If there is an original fact and subsequent fact rows for the same document reflect the net change from the previous state, it is transactional.
Re: transactional fact vs periodic snapshot fact
You may also build an accumulating snapshot if you want to investigate loan application performance metrics, i.e. how long app has been sitting in underwriting.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Similar topics
» Montly Snapshot views with transactional Fact table w/SCD2
» Transaction Fact or periodic snapshot fact
» Is this a Correct Periodic Snapshot Fact Table?
» Updating Periodic Snapshot Fact Tables
» Aggregates in Periodic Snapshot Fact Table
» Transaction Fact or periodic snapshot fact
» Is this a Correct Periodic Snapshot Fact Table?
» Updating Periodic Snapshot Fact Tables
» Aggregates in Periodic Snapshot Fact Table
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum