Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Sat, 21 Nov 2009 @ 14:10:04 GMT


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


Subj:   Re: Query tuning - same step running twice
 
From:   Victor Sokovin

  So per the above 31104 is locally built on AMP's - fine. So why is is AGAIN selecting * from 31104 and repeating the process and building the same locally on the AMP's. The row estimates are also the same and Step # 33 is turning out to be a bit costlier than Step # 32 . Why Step # 33 Any idea how this can be avoided .  


Do you see Spool 31104 mentioned anywhere further down in the Explain? Perhaps the optimizer needs it as a copy and performs some other steps on it.

If it is not mentioned again then copying it to Spool 31105 would be strange.


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