 |
 |
Archives of the TeradataForum
Message Posted: Fri, 26 Mar 2004 @ 14:19:20 GMT
| Subj: | | Re: Capturing Updates in a Readable File |
| |
| From: | | Victor Sokovin |
| | The catch in the approach would be , one can not know whether the apply the before-rows first or the after-rows first... | |
| | So definitely this WON'T WORK..... | |
And why is that?
The approach in the thread might have become somewhat complicated to follow because the posters wanted to include all types of DML. Let us, for
the sake of simplicity, go back to the original question. The OP has the after-image journal in place and wants only to rollforward the updates.
That should be possible by design of the journal. Usually the procedure is done to restore the whole table, though, based on some backup of the
table. The approach in the thread suggests that the changes can be restored using an empty table as such a "backup". If that works that would be
exactly what the OP wanted and it is likely to be faster than the full table restoration.
The same argument for rolling back deletes using the before-image journal but the OP was not interested in that.
If you have any practical reasons to believe the approach will not work with dual image journals please clarify.
Victor
| |
