Archives of the TeradataForum
Message Posted: Wed, 04 Feb 2009 @ 14:27:07 GMT
| Subj: || || Re: Capture commands run in exec macro |
| From: || || Rob Paller |
DBQL should capture the individual statements run in the macro from a performance/workload standpoint. Teradata has long encouraged the use of
macros as a means to extend security to users implicitly to allow them to manipulate objects they otherwise are not explicitly permitted to do
If you need to track the actions taken within a macro you could always introduce and audit table. Then place the necessary statements within
the macro to capture the USER executing the macro and the time which each step was completed.