Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 30 Jul 2004 @ 19:41:22 GMT


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


Subj:   Re: Impact of changing primary index on mload upsert
 
From:   Victor Sokovin

  What would be the impact of changing the existing primary index on a table with repect to mload upserts happening on that table.  


  We plan to change the primary index or add one more column to the primary index on table.  


  Would mload upserts fail?  


  If yes why and can we avoid it.? How?  



I seem to read the question differently than Michael does. In my opinion Michael has just explained that you cannot update PI values via the MultiLoad

     .BEGIN IMPORT.

My understanding of your question is that you want to restructure the PI (rebuild the table) and you are concerned about the existing ML upsert jobs. I'll try to comment on that. I think the jobs will start failing. I reserve a very little doubt as I did not try this with upserts yet but I did with updates and I am pretty sure that the behavior of ML will be the same.

ML fast-path updates require the full PI specification in the WHERE clause. If you modify the PI on the table (add or remove columns from the definition of the PI), you'll have to modify the update statements accordingly. Otherwise, they fail. So, modification of ML scripts seems to be the only remedy.


Hope this helps.

Victor



     
  <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