Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 05 Nov 2007 @ 15:07:10 GMT


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


Subj:   Re: Intercept the Teradata logon to run a script
 
From:   Anomy Anom

<-- Anonymously Posted: Mon, 5 Nov 2007 10:01 -->

Thanks for the feedback. All were useful and welcome.

Here's my view of the driving consideration:

The programmer's are trying to avoid fully qualifying the SQL (or the underlying views) with DB.Tbl.Col when dealing with multiple databases as sources of info for a query. After many iterations of operating with all necessary information in one database, they are looking at new applications that spread data across many databases.

Another constraint is that all logons are thru a homegrown application.

So, one option under consideration is to intercept the logon and assign the default DB as necessary.

MAY THIS BE DONE THRU A STORED PROC, FUNCTION, OTHER APPROACH?



     
  <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