Archives of the TeradataForum
Message Posted: Fri, 02 Jan 2009 @ 22:38:31 GMT
You could leverage step level query logging in DBQL for the userid running the stored procedure. Just be mindful of the volume generated with step level logging.
Aside from that a couple questions came to mind:
Are you doing any cursor processing in your stored procedure with a large number of iterations?
Are you sure that your process is not being blocked by another process?
Are you able to run an explain on the individual components of the stored procedure to make sure you don't have a bad product join?
Is it possible you are hot amping because of a bad PI value?
Hope this helps.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|