Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Wed, 20 Dec 2006 @ 18:33:54 GMT


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


Subj:   Re: Overhead For DBQ Logging Turned On
 
From:   Diehl, Robert

Anomy,

We have not seen any as long as you keep it cleaned up (moved to another database for reporting and trending). Since the location is DBC. You could go negative on Available space (from Transient Journal) in DBC which could prevent things, like Creating objects or granting rights. It also can prevent logons and queries if ACCESS logging is turned on. So best rule of thumb is to Keep Lots of extra space in DBC and clean up Query logs, Access logs, Resusage, logonoff, and Events on a regular basis. Also don't put 'SPOOL RESERVE' in a different database put it in DBC. 'SPOOOL RESERVE' is space some system administrators allot for Queries to run in. They sometimes put this in a database that no one has access too. They do this so queries always have space to run in as the system takes SPOOL SPACE and TEMP SPACE from all available free cylinders. It does not matter where the space is allocated.

We log all queires for all users. Only TPUMP is set to summary. We also run between 200,000 and 1,000,000 million tactical queries a day and get .02-07 second response on those depending on the query.

Of course it is hard to measure the impact in all areas if you do not have Query Logging on. Only way would be if you have other monitoring in place.

Even if it does add a bit of overhead, the benefits it adds are worth the overhead. And as you can see we are still getting good response on Tactical Queries.


Thanks,

Bob Diehl
Travelocity.com



     
  <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