Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Thu, 09 Feb 2006 @ 16:01:32 GMT


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


Subj:   PMON Logon source and Batch Account Tracking
 
From:   Anomy Anom

<-- Anonymously Posted: Thursday, February 09, 2006 10:57 -->

Hi Forum,

What I want to do:

Identify and or prevent batch accounts being used from desktops for query purposes by the same people who are responsible for the Batch ETL process.

Currently, When I see this happening I rely on the logon source in PMON or Teradata Manager and for certain tools I see a name associated with the IP but not in ervery case.

Our policy is and has been that this not allowed and that they (Support) should not be using this accounts due to the type of privs they carry. They do have other support type accounts they can use but they sometimes forget and are apologetic when caught. It's not good enough?

Is TDQM the answer? We are using DBQL but it's not preventive just diagnostic.



     
  <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