Subject | Re: [IB-Architect] Super-transactions and Incremental Backup |
---|---|
Author | dcalford |
Post date | 2000-06-21T02:09:46Z |
Hi Tim,
This is a very good idea (yea, I know it works cause it is one of our
maintenance systems when doing a snapshot-snapshot transition)
We have been doing this for about 4 months now with nary a problem.
I am glad that I am not off on a tangent when I see another person coming up
with the same sort of solutions to similar problems.
best regards
Dalton
Tim Uckun wrote:
This is a very good idea (yea, I know it works cause it is one of our
maintenance systems when doing a snapshot-snapshot transition)
We have been doing this for about 4 months now with nary a problem.
I am glad that I am not off on a tangent when I see another person coming up
with the same sort of solutions to similar problems.
best regards
Dalton
Tim Uckun wrote:
> Maybe we are trying to get too fancy here.
>
> Here is perhaps a too simplistic but maybe a useful approach.
>
> Problem: How to back up data that has been changed since some arbitrary
> defined date time:
>
> Solution: Every table has a field which stores a timestamp. The timestamp
> is updated on update or insert. The backup program is able to scan this
> field and back up only those records which fall in a predefined window.
>
> It won't solve all the problems but it's really easy to set up and may be
> good enough for most peoples needs. Of course this can be done with
> triggers now but it would be neat if the database engine could keep the
> timestamps up for you transparently.