Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 12 Apr 2005 @ 21:08:23 GMT


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


Subj:   Identifying Candidate Columns for Statistics
 
From:   Anomy Anom

<-- Anonymously Posted: Tuesday, April 12, 2005 12:53 -->

Hi,

Our database has more than doubled in the last few months, and is way too big for us to Collect Statistics on everything, so our approach is generally a 'best guess' based on expected table usage as to which columns are included in our Stats job when a table is implemented. (We then have a weekly Stats job which runs throughout Saturday and Sunday).

In recent times, as number of Users has increased, we've noticed an increasing need to add stats to columns which were originally excluded, and also to remove some which we thought might be beneficial, but aren't.

However, it is a very manual and tedious exercise to constantly review jobs on the box.

Has anybody out there got any clever way of looking at column access and then checking whether or not columns have stats? Or how does everyone else manage this?? (What we are ideally looking for is something we can automate on a weekly or monthly basis to throw out columns which would benefit from stats, but don't have them).

Any ideas/suggestions would be much appreicated!!



     
  <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