Archives of the TeradataForum

Message Posted: Mon, 20 Mar 2000 @ 16:23:57 GMT

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

I think that the main advantage is that once a global temp table is set up, you don't have to explicitly create it to use it. You can simply refer to it and it gets created on the fly. So, if you want to use the global temp table in a macro, you don't have to run a separate step to create the global temp table. You can just do an "INSERT" or "INSERT/SELECT" into it and it will be created dynamically as part of the macro execution.

We typically use global temp tables where users are executing a transaction that requires the use of a temporary table. Each session will automatically get an instance of the global temp table created as part of the transaction. I would use volatile tables more in a batch mode, so that the definition of the table is close to where it is used in the code. I would think that in most cases, the definition of global temp tables are controlled by the DBA's vs. the definition of volatile temp tables being controlled by the application developer.

Barry

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