Archives of the TeradataForum

Message Posted: Fri, 29 Aug 2003 @ 17:16:27 GMT

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

Karen,

With v2r4 there is no absolute way that I'm aware of using purely Teradata DBMS features. Obviously with v2r5 you've got query log.

Depending on how your system is setup and used you may be able to get close to it.

One customer I work with uses B.O. and they force it to logon/logoff for every query from the user. They then use dbc.logonoff to judge how long queries are taking.

If you use the ASE variables then you can get pretty close providing that when one query ends the next one starts immediately. Obviously that is not always going to happen, but sometimes it will. The same can be said of using Access Logging. As I said, it depends on your environment.

If you've got control over the code for your client tool then you can add a trap into that and record the elapsed time that way. If the client tool uses CLI (as opposed to odbc) then you can use the cli-sql exit and trap it that way. With either of these, you've then got to get that data from a file (probably on the user's pc) into a table on Teradata in order to make it really (IMHO) useable.

For requests coming in from a mainframe there's a tdp exit (can't remember which one) that gets passed the request parcel 'going in' and the success/error parcel 'coming out'.

Those are the choices that I'm aware of.

Cheers,

Dave

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