Studio fastload to volatile table

Teradata Studio
Junior Supporter

Studio fastload to volatile table

Was mentioned in a previous post that Studio 15.11 would bring ability to fastload to a volatile table.  

Was this feature implemented, and if so, how would it be initiated (i.e., volatile table would not be listed in browser to right click on).  

5 REPLIES
Teradata Employee

Re: Studio fastload to volatile table

Yes, this feature was added in Studio 15.11. There is a new toolbar button ("import" icon) in the Teradata SQL Editor. You will create your volatile table in the SQL Editor, then click the "import" icon. A drop down list is provided for you to choose your volatile table. Click OK and it will launch the Load Data Wizard.

Re: Studio fastload to volatile table

How fast is the Studio load to a volatile table?

Is it

1) Basically the same speed as Importing a file from SQL Assistant query

or is it

2) As fast as loading a file using Fastload?   

Junior Supporter

Re: Studio fastload to volatile table

It uses Fastload

Teradata Employee

Re: Studio fastload to volatile table

It does not use FastLoad. If the volume of data is large enough that you need FastLoad, you must use a "permanent" table as the target.

When Studio loads a volatile table it uses PreparedStatement batch insert. It should be similar to SQL Assistant with a .NET connection, faster than SQL Assistant with an ODBC connection.

Teradata Employee

Re: Studio fastload to volatile table

Reinforcing what Fred said -- the FastLoad wire protocol can only load data into a permanent table, not a volatile table. JDBC FastLoad, like all client implementations of the FastLoad wire protocol, is therefore limited to only loading data into a permanent table.

 

The reason why the FastLoad wire protocol is limited to only loading data into a permanent table is because the FastLoad wire protocol uses multiple sessions to load data. Multiple sessions can access the same permanent table, but a volatile table is only accessible to a single session that created it. A volatile table's very nature of being accessible to a single session is what prevents a volatile table from being loaded by the FastLoad wire protocol.