Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Thu, 26 Jan 2012 @ 09:43:31 GMT


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


Subj:   Identifying empty views, or conditions, that make the query fruitless
 
From:   Anomy Anom

<-- Anonymously Posted: Wednesday, January 25, 2012 20:46 -->

Folks

Not infrequently we run into situations where views on which a query is based, would be empty, because the base table in question is truncated and instead of view db.vw1, the view db.vw2 has data or within the view itself we have to refresh it with another base table

Or a filter condition has been wrongly written.

E.g. date column between date1 and date2, whereas it should be > date 2. Its easy to identify these causes if you Step through the components and then nail the problem down, like identifying a spark gone bad in your engine and as soon as you replace it, it starts right up.

I wonder if anyone had a chance to automate this process using some elimination method and an approach to the same.



     
  <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: 27 Dec 2016