Archives of the TeradataForum

Message Posted: Tue, 24 Oct 2006 @ 15:18:06 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Amit:

You saw the answer in your EXPLAIN. Since a macro is a transaction, it will execute statements like these from top to bottom. If your macro were doing something besides executing macros, there would be the possibility to do either multi-step (i.e. aggregation and spooling to prepare for a join) or multi-statement (i.e. 10 insert /selects become a single insert) processing. But otherwise, it wants to make sure that preceding steps worked successfully to minimize the amount of rollback should a step fail.

Since we do not know what is happening in each the other macros (LOAD1 thru LOAD6), we cannot address the potential for such parallel processing.

Hope this helps,

Michael Larkins
Certified Teradata Master
Certified Teradata SQL Instructor

	<Prev	Next>		<<First	<Prev	Next>	Last>>