Archives of the TeradataForum

Message Posted: Wed, 27 Mar 2002 @ 10:41:05 GMT

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

Volatile and Global Temporary tables are largely there for performance. Since by their very nature, they're neither persistent, nor accessible to anyone else, there're no security implications an hence no queuing on access to the accessrights table. Furthermore, there's no logging overhead in the transient journal. If the need for the data is restricted to the Teradata session, temporary tables are the way to go.

As for your existing ETL scripts, their designers may well have had valid reasons for using permanent work tables. First of all in an ETL activity, it's often necessary to re-visit the contents of intermediate result tables to resolve anomalies in the load. This wouldn't be possible with temporary tables. It's also possible that the ETL scripts were written prior to the availability of temporary tables at your site (it is a relatively recent feature - within the last 4 years).

Pat Belle
Teradata Certified Master

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