Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 05 Jul 2005 @ 22:54:09 GMT

  <Prev Next>   <<First <Prev Next> Last>>  

Subj:   Re: Transaction Rollback
From:   Dong, Charles J


Thank you for your comment.

Using FastExport and FastLoad/MultiLoad is an alternative. I believe it works faster. However, FastLoad requires that the table to be loaded be empty, and MultiLoad demands that there be no secondary indexes. This is not the real world we live in. What I want to do is to take advantage of transaction feature, i.e. rollback. For example, we can FastLoad a data set to a temp table, and then load the data in the temp table to the target table using INSERT INTO .. SELECT * FROM TempTable. The two step operation can avoid a lot of troubles if the operation fails. It will rollback automatically. And any existing secondary indexes can be kept in place. They are not needed to be dropped and recreated. Obviously, Teradata does not like to do this kind of operations.

For a data warehouse environment, loading and moving data are regular jobs. I just wonder which way Teradata likes. In addition to this problem, indexing, partitioning, querying, ... can make troubles to you if you do not do Teradata way. Not SQL way, only Teradata way? Then tell us, Teradata, what you like, and what kind of life we will have otherwise. We can try to work with Teradata.



  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023