Archives of the TeradataForum
Message Posted: Wed, 13 Jun 2001 @ 19:56:26 GMT
IF a lan session equates to a query, then can try the following;
1) set up your Teradata userid's with an accountname which includes &L. This will give you the session logon date/time in the dbc.ampusage accounting rows. This data tells you how much cputime and diskio's are used per amp per session.
2) use dbc.logonoff to find out how long the session was logged on for.
3) join these two pieces of information together on username and logondate and logontime and you get the information that you need.
IF not, then Teradata won't accurately give you the elapsed time of a query. You'd have to write a pre/post sql cli exit (if the exit point is available on unix) and tim eit manually.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|