Posted by vbnetguy on 05/18/06 02:13
Hi All, I have read MANY posts on how to track changes to data over
time
It appears there are two points of view
1. Each record supports a Change Indicator flag to
indicate the current record
(would this be EVERY table?)
2. Each table is duplicated as an archive table and
triggers are used to update archive
Can someone give me some guidance based on REAL world experience
which works best for them?
My scenario - I have insurance policies and must track history as
policies are updated by customer service reps.
Imagine many tables Policy>LifePol>LifePolRiders
>AccidentPol >etc...
>DIPol>DIPolRiders
To me the archive table scenario does not seem scalable at all....some
guidance on design would be aprreciated...Thanks!!!
Navigation:
[Reply to this message]
|