Archives of the TeradataForum

Message Posted: Fri, 05 Aug 2005 @ 16:07:44 GMT

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

<-- Anonymously Posted: Friday, August 05, 2005 10:56 -->

I am curious as I like to use volatile table in my work. I think that they wonderful and have never noticed a performance issue using them. Is there one? I'm from a user only viewpoint and not the DBA side.

I know that there are kept in spool space for the duration of the session or until dropped. I was under the impression that since they are basically a spool file there was no need to collect statistics as the optimizer treats spool files differently than other types of tables, perm or global temporary ones.

If you don't want or really need the table to be permanent I would suggest global temporary tables. You can collect statistics and at the end of the session the data goes away, just like volatile tables. You have to collect stats on the table definition first and then on the mat

I am curious as I like to use volatile table in my work. I think that they wonderful and have never noticed a performance issue using them. Is there one? I know that there are kept in spool space for the duration of the session or until dropped.

I was under the impression that since they are basically a spool file there was no need to collect statistics as the optimizer treats spool files differently than other types of tables, perm or global temporary ones.

If you don't want or really need the table to be permanent I would suggest global temporary tables. You can collect statistics and at the end of the session the data goes away, just like volatile tables. You have to collect stats on the table definition first and then on the materialized table after the table is populated.

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