Archives of the TeradataForum
Message Posted: Mon, 09 May 2005 @ 13:28:53 GMT
| Subj: | | Re: Keeping and re-using Tpump generated macros |
| |
| From: | | Geoffrey Rommel |
| | According to the Tpump documention (copied below), you can use the -m option to keep the generated macros in the database. Has anyone done
this? | |
Yes, although I agree with Kiki that it is a bit cumbersome.
1. Make sure that your script uses the optimum pack factor.
2. Run TPump with the -m option. This will cause the macros to be saved.
3. Revise your script. The script should be the same as it was before except that you replace the DML: instead of "insert ...", put "exec
macro-name insert". The last word tells TPump that the macro is going to do an insert.
| | If you do have to replace all your DML with macro commands, then what is the value of this option? | |
It saves time by not having to create and drop the macros. We used this on a job that ran every day in seven simultaneous streams, so the
overhead of creating the macros was significant. If your job is only one stream and runs once a week, don't bother.
One drawback is that maintaining the script becomes more difficult, so I recommend that you keep the original version of the script in your
source control library along with the macro version.
| 
