Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 10 Mar 2006 @ 21:28:41 GMT


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


Subj:   Re: Mload performance issue due to Secondary indexes
 
From:   Victor Sokovin

  But the Secondary index creation takes 4 hours.  


This is a serious problem for a daily load.

A 4-hour daily job is difficult to manage because in cases of its own failures or delays in preceding jobs you can easily run out of your loading window.

If you can't optimize index build time try to search for alternatives. Who are the end users of the table? Do all of them always require the whole table at a time? If not, you can perhaps split the table into a few smaller tables. This might suit the bulk of your users. A small minority might cope with doing UNIONs. You might still hear occasional protests from them but at least you place yourself in a *manageable* situation.


Regards,

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