Archives of the TeradataForum
Message Posted: Mon, 17 Jan 2005 @ 19:46:18 GMT
This is hokey, but worth a shot:
If applicable (granted, will not work for all cases), try placing the call statement for the stored procedure within a macro (simply pass the macro's parameters to the call statement.) Of course, I suppose (could be wrong...help please) this will turn the stored procedure into a single transaction (potential locking issues.) Also, you are limited to storing one call statement in a macro.
In this way, atleast the execute statement and parameters will be stored in DBQL.
Hope this helps,
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|