If you forgot the name you can get all the existing VTs in your current session using
HELP VOLATILE TABLE;
Thanks, dieter! Just what I was looking for.
Initially I tried
help database <user ID>;
which didn't go very well.
I am having a similar problem of not able to locate the volatile table created in the 'Database Explorer' of the 'Teradata SQL Assistant'. I want to select some column of the table just as the same way I can with the permanent database tables. I understand the volatile table is created in the user's SPOOL SPACE but where is this SPOOL SPACE loacted?
Can I see the volatile table created in the 'Database Explorer' of the 'Teradata SQL Assistant'?
Also, I know a volatile table can only be retained for the duration of the session (I assume it is the SQL session in 'Teradata SQL Assistant'), but if I created a volatile table thru SAS (using Teradata SQL connect), can I still see the volatile table data contents in 'Teradata SQL Assistant' if I don't end my SAS session? Just want to understand what do they referring a "session" as to?
Can someone get me a quick answer?
"where is this SPOOL SPACE located?" That's kind of like asking where your Azure or AWS database is located - it's kind of vague. All that can be said is that it is space dedicated to your user ID for this session. The Database Hierarchy shown in SQLA does not include your spool space. The only way to find it and display the structure is with the Help or Show SQL commands Dieter explained above.
Your SAS session is totally separate from your SQLA session. A session is the sequence of commands from an application's logging on to its logging off. (Furthermore, SQLA uses ODBC but SAS can use CLI.)
The intent of a volatile table is to simplify SQL processing by creating a reusable intermediate result set. The idea is that the application that creates it can reuse it. (Often this is done in a stored procedure, perhaps reused in a series of SPs.) If you want something more shareable and less volatile, consider a Global Temp Table instead.