Archives of the TeradataForum
Message Posted: Sat, 07 Apr 2007 @ 15:41:27 GMT
We often have the need to move "current" data into a historical table. The input volumes are large so insert/select combined with update operations are not viable due to transient journal considerations. The historical tables are large so it is not realistic to merge the current data and historical data together and dump the result into a new, empty, shadow (work) table due to the spool, CPU, I/O, and elapsed time required (as well as exclusive locks required for the subsequent drop/rename).
Today, we do use Fastexport to create a load ready file off the Teradata platform and then use MLOAD to apply the file to the target table.
Why would an MLOAD-like utility not be available that could perform the merge of any table into a target table? The source table would take the place of the work table used in the typical import-task MLOAD.
Has anyone seen a request for change in this area?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|