To access this download, you must login.

About this download

Teradata Studio is a client based graphical interface used to perform database administration tasks on the Teradata Database. 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.6 or later for Windows and Linux platforms. Mac OSX platforms 10.7 or greater does not provide an Apple JRE. Users must install Oracle's Java Developer Kit (JDK) 1.7 or 1.8 before installing Studio.

README

Teradata Studio 15.10.01 release information.

Supported Platforms:
====================================
     Windows Vista  - Microsoft Windows Vista Enterprise, 32-bit and 64-bit
     Windows Server - Microsoft Windows Server 2003, 32-bit and 64-bit
                                - Microsoft Windows Server 2008, 32-bit and 64-bit
     Windows 2000   - Microsoft Windows 2000, 32-bit
     Windows 7         - Microsoft Windows 7, 32-bit and 64-bit
     Windows 8         - 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 2.1, 3.0, and 4.0, 32-bit
                                - Red Hat Advanced Server 4.0, 64-bit
     Red Hat Platform - Red Hat Advanced Platform 5.0, 32-bit and 64-bit
     SUSE Linux Enterprise - SUSE Linux Enterprise 9, 32-bit and 64-bit
                                - SUSE Linux Enterprise 10, 32-bit and 64-bit
                                - SUSE Linux Enterprise 11, 32-bit and 64-bit
     Apple Mac            - OSX 10.7, 10.8, 10.9, and 10.10


Minimum Memory Required:
====================================
     4GB Memory, but 6GB Memory desired


Supported Teradata Databases Versions:
====================================  
     Teradata Database 13.10
     Teradata Database 14.00
     Teradata Database 14.10
     Teradata Database 15.00
     Teradata Database 15.10

Supported Aster Databases Versions:
====================================  
     Aster Database 6.0
     Aster Database 6.10
     Aster Database 6.20

Required Software:
====================================  
     - Java Runtime Environment (JRE) version 1.6, 1.7, or 1.8
     - Mac OsX 10.7 or greater does not provide the Apple JRE 1.6. Users must
     install Oracle's JDK 1.7 or 1.8
     - Mac OSX 10.8 needs JRE 1.7 or 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) Teradata Studio is installed in the Program Files directory.
        For example, C:\Program Files (x86)\Teradata\Client\15.10\Teradata Studio.
    When Teradata Studio is started, a 'workspace' directory is created in your
    home directory (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.15.10.01.01-1.tar.gz
        tar -xvf TeradataStudio__linux_x86.15.10.01.01-1.tar

    2) Change directories (CD) to the TeradataStudio.15.10.01.01 directory

        cd TeradataStudio.15.10.01.01

    3) Switch to Super User or Root and run the Studio install script, passing
       the Studio RPM (Package Management) package:

        su
        ./studioinstall TeradataStudio-15.10.01.01-1.x86.rpm

    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:

       . ./studio_uninstall.sh
 

Running Teradata Studio:
====================================
    Windows:
       Double click the Teradata Studio desktop icon shortcut.

    Linux:
       Update your path variable to include the TeradataStudio directory. Execute TeradataStudio.

    Mac:
       Execute Teradata Studio in the TeradataStudio directory.


JRE Location Changes:
=====================================
During the install of Teradata Studio, the JRE location is recorded in the TeradataStudio.ini file. This
.ini file is located in your install directory. On Windows for example, it is located at:
 
C:\Program Files (x86)\Teradata\Client\15.10\Teradata Studio

After you have completed the install of Teradata Studio and the TeradataStudio.ini is created, the location
of your JRE may change in the future if you automatically update the JRE revisions from the Oracle download site.
If your JRE location has changed, you should modify the TeradataStudio.ini file's reference to the JRE location:

For Example:

-vm
C:\Program Files (x86)\Java\jre7\bin\javaw.exe


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\15.10\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\15.10\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 15.10.01.01:

IDE-11494 - Studio Express install preconfigured connection profiles not all showing up
IDE-12305 (IDE-12328) - Data Lab View not showing Data Lab Groups or Data Labs
IDE-12023 - Change SQLA history import to use a mechanism other than the odbc-jdbc bridge, such as UCanAccess.
IDE-12318 - Studio, Studio Express JDBC version in preference page wrong


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. Teradata Studio
requires TDCH version 1.4.1. The following are the system requirements of TDCH 1.4.1:

    System
        JRE/JDK 1.6

    Supported Teradata Database versions:

        Teradata Database 13.10
        Teradata Database 14.00
        Teradata Database 14.10
        Teradata Database 15.00
        Teradata Database 15.10

    Supported Hortonworks Data Platform (HDP) versions:

        HDP 1.1.0.17 (Hadoop 1.0.3, Hive 0.9.0, HCatalog 0.4.0)
        HDP 1.3.2 (Hadoop 1.2.0, Hive(HCatalog) 0.11.0)
        HDP 2.1 (Hadoop 2.4.0, HiveServer2 (HCatalog) 0.13.0)
        HDP 2.1.3 (Hadoop 2.4.0, HiveServer2 (HCatalog) 0.13.1)
        HDP 2.3 (Hadoop 2.7.1, Hive 1.2.1, HBase 1.1.1)

    Supported Cloudera Hadoop (CDH) versions:
        CDH 4.3 (Hadoop 2.0, HCatalog 0.5.0)
        CDH 5.4 (Hadoop/HDFS 2.6.0, HBase 1.0)


Teradata Connector for Hadoop Setup:
====================================
The TDCH 1.4.1 must be installed and configured on the Hadoop system. Teradata Plugin for Eclipse's Smart Loader
for Hadoop 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 (version 1.4.1) onto your Hadoop system.
2) Navigate to the TDCH scripts folder in the TDCH install directory (default location: /usr/lib/tdch/1.4/scripts)
3) Execute the configureOozie.sh script as root user, providing the locations of your Hadoop services.
    
The usage of the configureOozie.sh script is as follows (this is all a single line):

    Usage: ./configureOozie.sh 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]
        [hiveMetaStoreKerberosPrincipal=hiveMetaStoreKerberosPrincipal]

(The parameters are entered on a single line. The parameters surrounded by [ ] are optional. The “[“ and “]” are not part of the command.)
(Note: the Job Tracker in HDP 1.x is now the Resource Manager in HDP 2.x)

    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 paarameter 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:
{
        "Distribution":"HDP",
        "DistributionVersion":"2.1",
        "TeradataConnectorForHadoopVersion":"1.4.1",
        "WebHCatalog":"hostname",
        "WebHCatalogPort":50111,
        "WebHDFS":"hostname",
        "WebHDFSPort":50070,
        "JobTracker":"hostname",
        "JobTrackerPort":8050,
        "NameNode":"hostname",
        "NameNodePort":8020,
        "NameNodeHA":"fs.defaultFS",
        "Oozie":"hostname",
        "OoziePort":11000,
        "HiveClientMetastorePort":9083
        "HiveMetaStoreKerberosPrincipal":"hive/_HOST",
        "KerberosRealm":"",
        "HiveMetaStore":"hostname"
}

** 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.