Archives of the TeradataForum
Message Posted: Fri, 27 Aug 1999 @ 15:29:53 GMT
This makes sense when you think about it. If you are updating an existing table (via update, insert or delete) and kill the update, Teradata is going to guarantee that the table will be recovered to its original state -- even across restarts.
One technique you can try is to design the queries to only insert rows into empty tables. In this case, Teradata will not log or go through a rollback, as Teradata knows that the original state of the target table is "empty."
If you have multiple steps that need to insert rows into the same table, you can either put all these steps into one multistatement request, or you can run multiple steps -- each inserting rows into their own empty table, consolidating the results at the finish.
If you have a need to update rows in the target table then you are going to have to live with the rollbacks. There is no way that I know of to "turn off" logging in this case.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|