To access this download, you must login.

About this download

Teradata Studio is an administration toolkit that helps users to create and administer database objects. It also provides a SQL Editor and Result Set Viewer for retrieving and displaying data fron your Teradata Database systems (Teradata, Aster, and Hadoop). It is built on the Eclipse Rich Client Platform (RCP). For more information on Teradata Studio, refer to the article Teradata Studio.

Teradata Studio contains several open-source components. A package containing the source code and licenses for these components is also available for download. This package does not contain proprietary Teradata source code.

Teradata Studio is a fully supported product by Teradata. 

For community support, please visit the Teradata Studio Forum.

► NOTE: This version requires Java Runtime Environment(JRE) 1.8. Mac OSX platforms 10.7 or greater does not provide an Apple JRE. Users must install Oracle's Java Developer Kit (JDK) 1.8 before installing Studio Express.


Teradata Studio 16.20.00 release information.
Supported Platforms:
     Windows Server - Microsoft Windows Server 2012 64-bit
                    - Microsoft Windows Server 2016 64-bit=
     Windows 7      - Microsoft Windows 7, 32-bit and 64-bit
     Windows 8 and 8.1 - Microsoft Windows 8 and 8.1, 32-bit and 64-bit
     Windows 10     - Microsoft Windows 10, 32-bit and 64-bit
     Ret Hat Server - Red Hat Advanced Server 6.0, and 7.0 32-bit and 64-bit
     Red Hat Platform - Red Hat Advanced Platform 6.0, and 7.0 32-bit and 64-bit
     SUSE Linux Enterprise - SUSE Linux Enterprise 11, 32-bit and 64-bit
    - SUSE Linux Enterprise 12, 32-bit and 64-bit
     CentOS 6       - 6, 32-bit and 64-bit
     CentOS 7       - 7, 32-bit and 64-bit
     Apple Mac      - OSX 10.7, 10.8, 10.9, 10.10, 10.11, and 10.12
Minimum Memory Required:
     4GB Memory, but 6GB Memory desired
Supported Teradata Databases Versions:
     Teradata Database 14.10
     Teradata Database 15.0
     Teradata Database 15.10
     Teradata Database 16.0
     Teradata Database 16.10
     Teradata Database 16.20
Supported Aster Databases Versions:
     Aster Database 6.20 
     Aster Database 7.0 (Aster on Hadoop)
Supported Hadoop:
     HDP 2.4, 2.5, 2.6
     Cloudera 5.8, 5.9, 5.11
Required Software:
     - Java Runtime Environment (JRE) version 1.8
     - Mac OsX 10.7 or greater does not provide the Apple JRE. Users must
     install Oracle's JDK (not JRE) 1.8.
Install Instructions;
     Download the Teradata Studio zip file from the download site.
  For Windows install:
     1) Unzip the Teradata Studio package to your local file system.
     2) Run the setup.exe to launch the Teradata Studio installation.
     3) Workspace location can be specified during installation.
     4) Teradata Studio is installed in the Program Files directory / Given directory.
        For example, C:\Program Files (x86)\Teradata\Client\16.20\Teradata Studio. 
When Teradata Studio is started, a 'workspace' directory gets created wherever you
specify or in your home directory if you don't specify(C:\Users\<user>\workspace-studio). 
This directory contains workspace files, including the SQL project folder.
The teradata.log file is located in the install \configuration directory.
  For Linux install:
    1) Unzip and untar the Teradata Studio package to your local file system.
        gunzip TeradataStudio__linux_x86.
        tar -xvf TeradataStudio__linux_x86.
    2) Change directories (CD) to the TeradataStudio. directory
        cd TeradataStudio.
    3) Switch to Super User or Root and run the Studio install script, passing
       the Studio RPM (Package Management) package:
        ./studioinstall TeradataStudio-
    4) Provide the path to where you would like to install Teradata Studio. 
       The default location is /opt/teradata. When Teradata Studio is started, a workspace 
       directory is created in the location where you launched Teradata Studio (TeradataStudio) from, 
       called workspace-studio. This directory contains workspace files, including the SQL project folder. 
       The teradata.log file is located in the install /configuration directory.
    Note: To check whether Teradata Studio is installed or not, run the following RPM command:
        rpm -qa TeradataStudio
    To remove the Teradata Studio product from your Linux system, run the following RPM command:
        rpm -e TeradataStudio
  For Mac OSX Install:
    1) Unzip the Teradata Studio package to your local file system.
    2) Double click on the Teradata Studio.pkg package to invoke the Teradata Studio installer
    3) You can change the install location or use the default install location, which is the
       /Applications/TeradataStudio folder. When Teradata Studio is started, a 'workspace-studio' folder 
       is created in the user's Documents folder. This folder contains the workspace files, including the
       SQL project folder. The teradata.log file is located in the install /configuration directory.
    To uninstall Studio on the Mac OSX, open a Terminal window and run the Studio uninstall script:
       . ./
Running Teradata Studio:
       Double click the Teradata Studio desktop icon shortcut.
       Update your path variable to include the TeradataStudio directory. Execute TeradataStudio.
       Execute Teradata Studio in the TeradataStudio directory.
Changing the Teradata Studio Workspace and/or Configuration information directories
    - (using Roaming Profiles):
When Teradata Studio is launched, it creates a workspace directory (called workspace-studio) in your 
USER HOME directory. If you want to change the location of your workspace directory, you must pass
the -data option into the TeradataStudio executable. You can do this by changing the Target parameter in the
Windows desktop shortcut or in the command window when launching Teradata Studio. For example:
"C:\Program Files (x86)\Teradata\Client\16.20\Teradata Studio\TeradataStudio.exe" -data "c:\Teradata Studio\My Workspace"
There is another directory (called .eclipse) created in your USER HOME directory that contains configuration 
information and jars for launching Teradata Studio. If you want to change the location of your configuration
directory, you must pass the -configuration option into the TeradataStudio executable. You can do this by changing
the Target parameter in the Windows desktop shortcut or in the command window when launching Teradata Studio.
For Example:
"C:\Program Files (x86)\Teradata\Client\16.20\Teradata Studio\TeradataStudio.exe" -configuration "c:\Teradata Studio"
You can combine both the -data and -configuration options on a single command line as well. This is often needed
when using a Roaming Profile that is not always accessible when running applications.
Bug Fixes
The following bugs were fixed in 16.20.00:
IDE-19867 SQL History Results message not incrementing STATEMENT number if failure
IDE-20004 Not able to create user in 16.20 database - Create user form is throwing exception
IDE-20623 Null pointer exception is getting while selecting SQL Tab in create new table form.
IDE-20291 Unable to drop the MR Function using DSE menu option
IDE-19853 Same keyboard shot cut key is using in two different place in new hadoop connection profile.
IDE-20441 Wrong sort order in Teradata Studio 16.10 with German Settings in Data Format
IDE-20442 SQL Editor contents lost if selected text contains empty line
IDE-19799 Null value of varchar data type transferred to empty string in Copy table
IDE-20460 Table Data Load don't create error file if uncheck 'Stop Loading...' option
IDE-20461 Table Load when processing error rows needs to stream to output file
IDE-20678 Copy Table data does not work on Mac
IDE-20799 Mac OSX: Studio: Unable to import Excel file via Data Transfer when source folder has Japanese characters
IDE-20090 Not able to data transfer with Create Table option from TD 16.10 database to TD 15.10
IDE-20088 Getting Dependency Browser warning from compare object definitions dialog
The following improvements were made in 16.20.00:
IDE-18970 Teradata 16.20 Parser Update
IDE-19032 Support Time Series
IDE-17726 Support Foreign Server Objects Display in DSE
IDE-18774 Added Ability to add own JDBC Properties for Knox
IDE-19891 Improved Connect Through Privileges Form
IDE-14661 Improved Logon Privileges Form
IDE-17758 Added Creation Timestamp Column for Views & Tables in object list viewer
IDE-18219    Support to select custom workspace location
IDE-10510 Provided support for Teradata LDAP connections to TDCH
IDE-15048 Provided support for Hive on Cloudera
IDE-17895 Provided Columns & Attributes information in View Form.
IDE-18178 Added support to recognize the Custom Date Formats
IDE-17729 Improved Loading Objects in DSE for Hive connection
IDE-17730 Improved Loading Objects in DSE from Impala connection
IDE-20439 Improved SSL connection timeout handling to not prompt for the password after timeout
Hadoop Configuration Support:
Teradata Studio provides an option to transfer data to and from Hadoop systems using its feature called the
Smart Loader for Hadoop. The Smart Loader for Hadoop uses the Teradata Connector for Hadoop (TDCH), which is
installed on the Hadoop node, to provide the data transfer to and from the Hadoop system. The following are the system requirements of TDCH:
    Supported Teradata Database versions:
        Teradata Database 14.10
        Teradata Database 15.0
Teradata Database 15.10
        Teradata Database 16.0
        Teradata Database 16.10
Teradata Database 16.20
    Supported Hortonworks Data Platform (HDP) versions:
        HDP 2.4, 2.5, 2.6
    Supported Cloudera Hadoop (CDH) versions:
        CDH 5.8, 5.9, 5.11
Teradata Connector for Hadoop Setup:
The TDCH must be installed and configured on the Hadoop system. Studio
uses Oozie to submit the data transfer workflow on the Hadoop System. Please follow these instructions
to configure the Hadoop System and create the Oozie workflow files.
1) If the script is not already on your Hadoop system, download and install the TDCH onto your Hadoop system.
2) Navigate to the TDCH scripts folder in the TDCH install directory (default location: /usr/lib/tdch/1.5/scripts)
3) Execute the script as root user, providing the locations of your Hadoop services.
The usage of the script is as follows (this is all a single line):
    Usage: ./ nn=nameNodeHost [nnHA=fs.default.value] [rm=resourceManagerHost] [oozie=oozieHost] [webhcat=webHCatalogHost] [webhdfs=webHDFSHost]
        [nnPort=nameNodePortNum] [rmPort=resourceManagerPortNum] [ooziePort=ooziePortNum] [webhcatPort=webhcatPortNum] [webhdfsPort=webhdfsPortNum] 
        [hiveClientMetastorePort=hiveClientMetastorePortNum] [kerberosRealm=kerberosRealm] [hiveMetaStore=hiveMetaStoreHost] 
(The parameters are entered on a single line. The parameters surrounded by [ ] are optional. The “[“ and “]” are not part of the command.)
    nn - The Name Node host name (required)
    nnHA - If the name node is HA (High Availability), specify the fs.defaultFS value found in core-site.xml
    rm - The Resource Manager host name (uses nn parameter value if omitted)
    oozie - The Oozie host name (uses nn parameter value if omitted)
    webhcat - The WebHCatalog host name (uses nn parameter value if omitted)
    webhdfs - The WebHDFS host name (uses nn parameter value if omitted)
    nnPort - The Name node port number (8020 if omitted)
    rmPort - The Resource Manager port number (8050 if omitted)
    ooziePort - The Oozie port number (11000 if omitted)
    webhcatPort - The WebHCatalog port number (50111 if omitted)
    webhdfsPort - The WebHDFS port number (50070 if omitted)
    hiveClientMetastorePort - The URI port for hive client to connect to metastore server (9083 if omitted)
    kerberosRealm - name of the Kerberos realm
    hiveMetaStore - The Hive Metastore host name (uses nn parameter value if omitted)
    hiveMetaStoreKerberosPrincipal - The service principal for the metastore thrift server (hive/_HOST if ommitted)
The port numbers are HDP’s defaults. So, if the system being set up has all the services
hosted on a single system on the default ports, only the nn parameter is needed.
The script will exit with an error message if the TDCH is not in its expected location.
Otherwise the script will display a message indicating the parameters values. A sample
message is as follows:
The following is the specification of the Hadoop services used by the Oozie workflows:
** You must also make sure the Teradata IDE/Studio client machine can access the Hadoop system services (hostnames and ports provided to configureOozie script).
Thus, you may need to add the Hadoop services host names and IP addresses to your host file or DNS service. 
The certificate used by the Knox server needs to be added to the Java runtime's certificate store. You can save the certificate with a web browser. 
For example, with Chrome, you can:
Enter the Knox server:port in the address bar. It will say that the connection is not private
Click Advanced, then click on the Proceed to site link
Click on the lock in the address bar and select Details
Click View certificate
Select the Details tab in the resulting dialog and click the Copy to file... button
In the resulting Certificate Export Wizard, save the certificate as Base-64 encoded
(Other browsers have similar methods to get to the Certificate Export Wizard)
Alternatively, on the Knox server, run the command:
     keytool -export -alias gateway-identity -rfc -file knox.crt -keystore <path to gateway.jks keystore (eg. /usr/lib/knox/data/security/keystore/gateway.jks)>
To install the certificate into your Java Runtime certificate store, run the command:
     %JDK_HOME%\bin\keytool.exe -importcert -alias "TDH240 Knox self-signed certificate" -file cert_location/<filename>.txt -keystore %JRE_HOME%\lib\security\cacerts
Where %JDK_HOME% is an environment variable with the location of a JDK and %JRE_HOME% is the location of the JRE used to run Studio.
The keytool.exe will ask for the password to the certificate store. It is “changeit” unless you’ve changed it