Archives of the TeradataForum
Message Posted: Fri, 16 Mar 2001 @ 19:16:59 GMT
Dave is absolutely right about &I. Specifically, it expands to the following:
0000 is the host number
Request number behaves much like session number in that it is a sequentially assigned number that starts back at one at some point.
Something to be aware of when using &I. the system will create a set of rows for EVERY request. That includes the LOGON request. Typically, if you were to logon through BTEQ and run one query, you would end up with two sets of rows in DBC.ACCTG. One for the logon and one for the actual query. Also, the request number will not necessarily start with one and increment by one. I usually use the RANK function to get the sequential ordering.
Using the ACCLOGTBL with the results from DBC.ACCTG is very powerful when you use the &I ASE variable. By joining the UserName and AccountName between the two tables, you can definitively associate the resource consumption with the specific query.
On the topic, I'd like to get a sense from everyone as to how many people are using &I and to capture request level resource consumption details. Also, are people using it for performance tuning???
Thomas F. Stanek
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|