Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Wed, 22 Jan 2003 @ 20:19:34 GMT

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

Subj:   Re: Architechtural question--How to account for application usage?
From:   John Adams

  -------Original Message-------
From: David Wellman

  Not simple. As you're talking about DSN's I'm assuming that the applications are going through ODBC.  


  If the application is bought in (e.g. Business Objects)  

Great guess! And Brio.

  and the user gets presented with an Teradata/ODBC logon screen then what's to stop them using the wrong AccountName? Probably nothing, which means that you may not be able to rely on the figures.  

True. This is why I was thinking of putting in separate DSNs for each application, each of which has the appropriate account string defaulted. That fixes issues of carelessness and ignorance, but does nothing to fix deliberate misuse by a user.

(Surely _our_ users wouldn't do any such thing!)

I _was_ wondering whether there was a way to lock down the DSN so that the account string can't be changed. Again, a malicious user could create a DSN with a wrong account string and use that, but it increases the effort required to misbehave.

  If the application is home-grown then you can (presumably) get the code altered to force the correct AccountName based on the application. This will give you the breakdown that you're after and is probably the simplest way.  

If we only grew our own applications! So this can't be forced using Brio/BusinessObjects--can it in some other app?


John A

  <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: 28 Jun 2020