Teradata’s latest and greatest Eclipse offering has been released and is available in the Teradata Developer Exchange download section at Teradata Plug-in for Eclipse . The 15.00 release builds on the 14.10.01 offering by boasting increased functionality.


What's New:

  • Aster 6.0 Support

Added support for the Aster 6.0 Database and embedded the Aster 6.0 JDBC Driver.

  • Aster Smart Loader, Table Load and Export Wizards

Smart Loader, Table Load and Table Export Wizards now support the Aster Database. Users can invoke the load and export wizards from the Data Source Explorer or the new Data Transfer Wizard.

  • Aster Table Editor

The Teradata Studio Table Editor has added support for Aster tables. Users can invoke the Table Editor by selecting the table in the Data Source Explorer and choosing the Data>Edit Data option. The Table Editor supports paging and filtering of data for large tables.

  • Teradata 15.00 Support

Added support for the Teradata 15.00 Database. This includes support for the 15.00 Teradata grammar in content assist, as well as support for JSON data types. Teradata Studio 15.00 has also embedded the Teradata 15.00 JDBC Driver.

  • Aster Drop Action

Support for dropping of Aster objects has been added to the menu and toolbar actions.

  • Hadoop Enhancements

Hadoop connections have been added to the list of Connection Profile Types and are now displayed in the Data Source Explorer, as well as Hadoop object details are displayed in the Object Viewer.

  • Data Transfer Wizard

Teradata Studio 15.00 has added a Data Transfer Wizard that provides a single dialog for transfering data between Teradata, Aster, Hadoop, and the external file system. Users can use the Data Transfer Wizard to invoke the Smart Loader on Teradata or Aster Databases, load or export table data for Teradata or Aster Databases, and Copy table objects and data between Teradata Databases or Teradata and Hadoop.

  • New Teradata Compare Object Wizard

A new Compare Object wizard is provided to compare a Teradata object with another like object in the same or a different Teradata Database. The DDL for the objects is displayed side by side in the Compare Editor with the differences highlighted. Toolbar buttons are provided to allow the user to move from one difference to another.

  • New Teradata Copy Object Wizard

The new Copy Object Wizard allows users to copy Teradata  Database objects from one Teradata system to another. The Copy Object Wizard is invoked by dragging one or more objects from the Data Source Explorer to the Transfer View or via the Data Transfer Wizard. The Copy Object Wizard provides filtering of columns and data when copying table objects.

  • SQL Editor Enhancements

The SQL Editor has been enhanced to provide an Auto-commit toggle, Commit and Rollback toolbar options. This enhancement allows the user to manually manage the "commit" operation on their SQL statements. By default, the Auto-commit option is on. The user can toggle Auto-commit off and manually commit or rollback SQL statements to the database.

Another SQL Editor enhancement is the ability to link a SQL Editor window to a Result Set Viewer window. This allows the user to better manage multiple SQL Editors and Result Set Viewers.

  • Disk Cache

Allows large objects, such as CLOBS, BLOBS, JSON, or large text data types to be cached on disk for Export, Load, and Editing.

  • TPT Editor

The Teradat Plugin for Eclipse 15.00 includes a TPT Editor that provides smart editing of TPT scripts and JVF files. A new TPT Perspective is provided that presents a Navigator, Problem and Markers window, Script editor, and Outline view. A TPT parser is embedded to provide content assist when entering your TPT script. Script syntax coloring, error markers, and an outline view are also provided to help the user build their TPT and JVF scripts. 

Need Help?

If you are new to the Eclipse world, there is an article to help you get up and running. Please refer to Getting Started with Teradata Plug-in for Eclipse. To ask questions or discuss issues, refer to the Teradata Studio Forum and post your question.

Online Help can be accessed within the plug-in in two ways:

  • From the main menu: Help > Help Contents > Teradata Plug-in for Eclipse
  • Context sensitive help: When a user is in a dialog, they can hit the F1 key to retrieve help text sensitive to where they are within the dialog.

Reference Documentation can be found on the download page or at: www.info.teradata.com

  • Title: Teradata Studio, Studio Express, and Plug-in for Eclipse Release Definition Publication ID: B035-2040-014C
  • Title: Teradata Studio, Studio Express, and Plug-in for Eclipse Installation Guide Publication ID: B035-2037-014K
smshakil 1 comment Joined 04/12
27 May 2014

TeradataStudio__win64_x86., does not show list of all schemas. but when i reinstalled 14.01 it shows. please let me know how to show all list of schemas in 15.0

fgrimmer 660 comments Joined 04/09
27 May 2014

Shamim, There is a preference to change the Data Source Explorer display back to flat instead of hierarchical. Go to Window>Preferences. Choose Teradata Datatools Preferences>Data Source Explorer Load Preferences. Uncheck "Show Databases and Users in Hierarchical Display".

rechenw 2 comments Joined 04/14
05 Mar 2015

@fgrimmer, if we are running Teradata version 14(.10.0.04), do we have to stick with version 14 of the Eclipse plug-in, or is version 15 of the plug-in backwards compatible with Teradata 14?

fgrimmer 660 comments Joined 04/09
06 Mar 2015

@rechenw, Teradata Plugin for Eclipse version 15.00 is backword compatible with Teradata 14.00. It supports Teradata versions: 13.00, 13.10, 14.00, 14.10, and 15.00

rechenw 2 comments Joined 04/14
09 Mar 2015

Great, thank you!

slemme 5 comments Joined 08/11
24 Mar 2015

I have successfully deployed a Java UDF (TD 14.10) without the Eclipse plug-in or javFnc.jar, but now I am trying to return a Clob.  I have tried compling it standalone in Eclipse (just adding needed jars to my build path) and installing the full stack (Eclipse Kepler, this plug-in, Java 7 compiling in 1.6 compability mode) but I get the same problems when running main() from within Eclipse.  I don' t know if its the code or my environment/configuration.  Any assistance is appreciated.
import java.sql.Clob;
//import com.teradata.fnc.Clob;
public class CreateClob {
       static boolean test_mode=false;
       public static void main(String[] args) {
              java.sql.Clob result = getContent("mystring");
              System.out.println("The Clob="+result);
    public static java.sql.Clob getContent(String content) {
          try {
                 java.sql.Clob response = com.teradata.fnc.Clob.getUDFOutputClob();
                 // Eventually, populate new Clob with large XML from a web service
                 response.setString(0, content);
                 return response;    
          catch(Exception e) {
                 if (test_mode) {
        return null;
With javFnc.jar only:
Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
       at com.teradata.fnc.Clob.<clinit>(Clob.java:52)
       at createClob.getContent(createClob.java:24)
       at createClob.main(createClob.java:17)
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
       at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
       at java.security.AccessController.doPrivileged(Native Method)
       at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
       at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
       ... 3 more
Adding slf4j-api-1.6.1.jar I get a different problem:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Exception in thread "main" java.lang.UnsatisfiedLinkError: com.teradata.fnc.FNCcall.wrapper_FNC_function([B)Ljava/lang/Object;
       at com.teradata.fnc.FNCcall.wrapper_FNC_function(Native Method)
       at com.teradata.fnc.FNCcall.FNC_GetJavaUDFOutputLobCrtContext(FNCcall.java:224)
       at com.teradata.fnc.LobFactory.createClob(LobFactory.java:145)
       at com.teradata.fnc.Clob.getUDFOutputClob(Clob.java:246)
       at CreateClob.getContent(CreateClob.java:14)
       at CreateClob.main(CreateClob.java:8)

fgrimmer 660 comments Joined 04/09
30 Mar 2015

Scott, Below is response from developer...
"getUDFOutputClob should be used as part of UDF function and cannot be used in standalone application as it consists of native function calls and is dependent on some of the libraries provided by Teradata Database. It is supposed to work only on the DBS site with TD installed.
Error is observed in com.teradata.fnc.FNCcall.wrapper_FNC_function  call.
The function FNCcall.wrapper_FNC_function is  from Javfnc.jar is a JNI function call and it depends on some libraries  provided by database . These libraries are  not  exposed to an application.
It will work only through UDFs deployed on Teradata Database.
Also setString should be called with the first parameter value equal to 1. The customer called the function with the parameter value equal to 0.
I am able to successfully deploy JAVA UDF which uses com.teradata.fnc.Clob.getUDFOutputClob() to return CLOB object.

slemme 5 comments Joined 08/11
31 Mar 2015

Thank you!  I was coming to the same conclusion -- javFnc.jar is sufficient for compile time but not for run time.  I was trying to follow the documented best practice of testing outside the database first, but this is an instance where I will have to look at using debugging/trace functions within the database (excerpt below is from 14.10 SQL External Routine Programming doc).
Debugging a Java method that Teradata Database executes as a UDF is limited.
Debugging Outside the Database
The best practice is to develop and test the method outside the database. You can use your own debugging tools to verify functionality.
Be sure your tests include the following:
• Limit checks on the input values
• Limit checks on the return value (for scalar and aggregate UDFs) or on the output argument values (for table UDFs)
• Proper handling of NULLs
• Exception handling
Using Trace Tables
If debugging outside the database is not sufficient, you can use trace tables to get trace diagnostic output. Debugging UDFs using trace tables is similar to debugging external stored procedures using trace tables. For details, see “Debugging Using Trace Tables” on page 314.

You must sign in to leave a comment.