Archives of the TeradataForum
Message Posted: Tue, 29 May 2001 @ 22:50:14 GMT
The fact that the processing is in a macro means it is in the same transaction, thus ALL changes are transient journalled for ALL the statements including delete all!.
If you can run the process not in a BT/ET scenario, e.g. in a ordinary BTEQ script using Teradata commit type processing then this will get round the Transient Journal issue.
Another option is to create the Volatile table with the NO LOG option, this stops the data being transient logged. I have not tried it in a BT/ET (same as Macro) type environment but recommended it in have stand alone situation where multiple inserts and updates were being applied to the table and got tremendous performance improvements 1hr+ => 1min!.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|