Database Reference
In-Depth Information
Collection A
Collection B
Collection C
Note that it is not uncommon for a collection to have more than type of history requirement
such as
Customer
requiring a Type 1 for
customerLastName
and a Type 2 for
emailAd-
dress
. Also, the thought process for this step is the same for both relational and dimensional
physical data modeling, so let's look at an example of each.
For Relational
Here is the completed Collection History Template for our Account example:
Account Project Collection History
Store only the original
state
(Type 0)
Store only the most current
state
(Type 1)
Store full his-
tory
(Type 2)
Store some his-
tory
(Type 3)
Customer
✓
AccountOwnership
✓
Account
✓
WithdrawalDebit
✓
DepositCredit
✓
InterestCredit
✓
CheckDebit
✓
