< DATE-120" (just an example!) for the LogOnOff, ResUsage, AccessLog, etc. tables, where the relationships to other tables seem to be zero (those are simple logging tables). Even the multiple QueryLogging tables, while related to each other and Db..." />
 
Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 08 Apr 2005 @ 12:44:54 GMT


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


Subj:   Re: System Table Maintenance
 
From:   Harold D Kleven

We run a daily script to do "DELETE ... WHERE <DATE> < DATE-120" (just an example!) for the LogOnOff, ResUsage, AccessLog, etc. tables, where the relationships to other tables seem to be zero (those are simple logging tables). Even the multiple QueryLogging tables, while related to each other and Dbase, are simply logging tables and can be cleaned out by date (so long as you clean out all at the same time). All of the rest of the tables

seem necessary to keep in sync with others and seem related to some ordinary function (schema maint, permissions, etc.) so simply keeping current on the business/DBA functions would keep them current.

Before we completly clean them out, we capture certain "key" statistics to our own statistics history - sorta a "small version" version of the full table so we can still do multi-year reporting and see some comparison stuff.



     
  <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: 23 Jun 2019