Archives of the TeradataForum

Message Posted: Wed, 12 Nov 2003 @ 02:31:46 GMT

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

A volatile table occupies spool space (or maybe temp space) within the session of the user.

A 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".

When the session is terminated (i.e. the user logs off), the volatile table is destroyed.

Your stored procedure should be able to access the volatile table provided that the volatile table creation and the stored procedure call occur within the same Teradata session.

If you are using volatile tables, you probably will need to understand the clause "ON COMMIT PRESERVE ROWS". In basic terms you need to use this clause to ensure that any data you load into the volatile table is hangs around so that the next query can use it. If you don't use the clause, you may well find that your volatile table is empty - no matter how many rows you insert into it!

Hope this helps.

Glenn Mc

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