 |
 |
Archives of the TeradataForum
Message Posted: Wed, 25 May 2005 @ 17:08:55 GMT
Subj: | | Re: DBC.AMPUSAGE and request CPU totals |
|
From: | | Thomas F. Stanek |
AMPUsage (DBC.ACCTG) is updated at the completion of each query step per AMP. If a query fails, the currently processing query step is not
recorded in AMPUsage. In other words, if a query has 12 steps and it fails while processing step 7, only the resource consumption for the first 6
steps are recorded in AMPusage. Keep in mind that if some of the AMPs completed processing of step 7 before the query aborted, that resource
consumption data would be recorded on those AMPs.
I hope that helps.
Regards,
Thomas F. Stanek
APP Consulting, Inc.
| |