Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Thu, 04 Sep 2003 @ 17:26:42 GMT


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


Subj:   Re: Query Logging
 
From:   Claybourne Barrineau

Ian,

We haven't noticed a significant difference in response times (knock on wood) so far. We have turned on Query Logging for just our on- line users (as defined within our account string definitions.) Because we are running TPump with some of our Batch-IDs, we couldn't afford to turn on query logging for all IDs.

We still use Access Logging to track drops, deletions, etc. for most of our production objects. This function of Access Logging is still vital and is not replaced by Query Logging unless we turned query logging on for all ids (which we cannot because of Tpump and some various other reasons.)

Looking forward to 5.1, when Query Logging will track CPU and IO (by step!) However, as a friend as pointed out, only the top and bottom 5 amps and an average will be tracked for CPU and IO; thus, AmpUsage will probably still be needed in the future.

We are pleased with the results so far. Now we need to focus on turning all of this data into workable information!


Thanks,

Clay



     
  <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