Home Page for the TeradataForum
 
https:

Archives of the TeradataForum

Message Posted: Fri, 17 Aug 2007 @ 16:35:17 GMT


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


Subj:   Re: Update vs Delete/Insert
 
From:   David Clough

Oddly enough, we're now doing the reverse. We used to Delete and Re-Insert but, having done some testing on the performance of Updates, we're changing our process to Updates. It's no faster, but neither is it noticeably slower.

What Updates do give you is a situation whereby the row is not removed at the same time a User is running a query (with Locking Row Access) only to find that certain rows are missing !

Personally, I'd recommend that you stick with Updates but try to ensure that Work table and Target table are on the same Amp.

Hope that helps.

Dave Clough
Database Designer
Express ICS

www.tnt.com



     
  <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: 28 Jun 2020