Archives of the TeradataForum

Message Posted: Wed, 10 Aug 2005 @ 13:28:47 GMT

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

In the words of the Cowardly Lion, I'd turn back if I were you.

ETL tends to be heavy in both I/O and CPU. Maybe your Teradata system is large and can handle the extra load, but it is more common nowadays to push the transforms to another server and load the data in its final form into Teradata, thereby reserving the Teradata box for pure warehousing.

If you must put the ETL transforms on Teradata, and (as you say) no cursors are required, I would favor views over macros and macros over stored procedures. SP's are great when they're really needed, but if you're simply encapsulating a series of SQL statements they offer no benefit over macros.

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