Archives of the TeradataForum

Message Posted: Wed, 12 Nov 2003 @ 19:03:43 GMT

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

Re

"volatile table is not accessible from one session to another. For example, if user A logs on and creates a volatile table X and inserts some data into it, then logs on a second time and creates another volatile table X and selects data from the second table, it will be empty because the two volatile tables are not the same "table"."

Note, in order for a stored procedure which creates a volatile table to successfully compile, the "create volatile... " statement needs to be copied and executed before the compile statement. Still, a warning will result, but the compile will be successful. Sort of a "chicken vs. the egg" problem.

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