Archives of the TeradataForum

Message Posted: Mon, 20 Jul 2009 @ 16:02:01 GMT

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

<-- Anonymously Posted: Monday, July 20, 2009 11:59 -->

A macro is a "multistatement request", so the optimizer builds the combined access plan when the macro is first invoked. Random AMP sampling would be done at that time, prior to executing any of the statements. (There's no pre-compile.)

A potential workaround for your specific case might be to populate the permanent work tables with "typical" data, collect stats, then delete the rows from the tables.

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