Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Wed, 24 Jul 2002 @ 15:44:14 GMT


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


Subj:   Re: Access Logging and changing the log table
 
From:   Walter, Todd A

Don't do that! It will not be pleasant.

There is a reason for the PI on the table. It causes all the rows for a session to go to the same AMP which in turn allows the implementation of FIRST, LAST and BOTH logging. Otherwise it would be difficult or impossible to identify the log rows that should be tossed. FIRST, LAST and BOTH were were requirements from the security folks.

Just to make clear, the hot amp issues on access log occur only when a very large number of requests are submitted on the same session. It is not clear that these requests should be logged in the first place (eg TPump, BTEQ import or Bulkload sessions).

Good news is... In V2R5 there will be a Query Log. It will do the things people have been trying to do with Access Logging (but which it was never designed for) and the A.L. can go back to being for the security administrator. The QL has fixed these issues and added a bunch of stuff y'all have wanted for some time (like response time for instance).



     
  <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