Teradata Studio is a client based graphical interface used to perform database administration tasks on the Teradata Database. Teradata Studio is built on the Eclipse® Rich Client Platform (RCP), taking advantage of the RCP framework for building and deploying native GUI applications. It extends the Eclipse Data Tools Platform (DTP) to enhance Teradata Database access. Teradata Studio can be run on Windows, Linux, and Mac OSX operating systems. The Eclipse platform is designed as an open tools platform but architected so that its components (or a subset of its components) can be used to build RCP applications. This allows Teradata Studio to benefit from the many high quality Eclipse features available while focusing on value-add for Teradata.

Teradata Studio includes the following key features:

  • Task-based Perspective Display.
  • Modular display that allows you to move panels around, creating a custom look and feel.
  • Data Source Explorer to view database objects, such as databases, schemas, tables, macros, stored procedures, map reduce functions, user-defined functions, user-defined types, views, and triggers.
  • Connection Profile Wizard to create connection profiles using the embedded Teradata or Aster JDBC Driver or Hadoop connection service.
  • SQL Editor to create, modify, format, and execute SQL queries.
  • SQL Query Builder to visually build and edit SQL queries (Teradata only).
  • AutoCommit options allows user to manually control autocommit of SQL Statements.
  • Result Set Viewer that displays result set data, allowing the user to select rows and cells, copy and format data, sort, hide, and move columns, and search for result set data values
  • Export Result Sets to Excel, XML, or text files
  • SQL History to maintain a historical record of submitted SQL queries with timings and status information
  • Object Viewer to display information about Databases, Users, Schemas, Tables, Views, Map Reduce Functions, Macros, Stored Procedures, User Defined Functions, User Defined Types
  • Drop Databases, Schemas, Tables, Views, Stored Procedures, Macros, or User Defined Functions
  • Data Transfer Wizard to transfer table data between Teradata, Aster, Hadoop, and the external file system.
  • Data Export wizard to extract data from the Teradata or Aster Database to a file on the desktop.
  • Data Load wizard to load data from the desktop file system to the Teradata or Aster Database.
  • Smart Loader to easily load delimited text or Excel files into Teradata or Aster.
  • Table Data Editor to easily Update, Insert, or Delete data for a table.
  • Transfer History View to display the information about data transfers.
  • Copy Object Wizard to copy Teradata objects from one Teradata system to another.
  • Hadoop Transfer Wizard to transfer Hadoop tables between Teradata and Hadoop (aka Smart Loader for Hadoop).
  • Compare Objects Wizard to compare Teradata database object definitions

Teradata Database Only Features -

  • Create Dialogs: Databases, Users, Tables, Views, Stored Procedures, User Defined Functions, and User Defined Types
  • Modify and Drop Dialogs: Databases and Users
  • Administer Dialogs: Roles and Profiles
  • Grant or Revoke of access and system rights
  • Manage Privileges on database objects
  • Copy Table, View, Stored Procedure, Macro, or User Defined Type definitions to another database, or to another system
  • Compare database object DDL between two database objects
  • Rename Tables, Views, Stored Procedures, Macros, or User Defined Functions
  • Data Source Explorer menu options to run Stored Procedures, Macros, and User-defined Functions
  • Move space from one database to another
  • Find objects in the Data Source Explorer
  • Set up the rules for Query and Access Logging

For administrative functions, Teradata Studio will provide a preview of the SQL statements and allow the user to save the SQL to a file or display it in the SQL Editor.

Usage Videos

For detailed step-by-step demonstration of the Studio features, refer to the Studio Usage Videos article.

Studio Perspectives

A perspective is a visual container for a set of views, menus, toolbars, and actions.  Each perspective provides a set of functionality aimed at accomplishing a specific type of task or works with specific types of resources. Teradata Studio includes three perspectives: Query Development, Administrator, and Data Transfer. The Query Developement perspective focuses on SQL query developement tasks. The views displayed within the Query Development perspective include the Data Source Explorer, Project Explorer, SQL Editor, Result Set Viewer, and SQL History View. The topmost menus provide the user with tools to create and edit SQL statements.

The Administrator perspective focuses on database development and administrative tasks for your Teradata Database.  The Administrator perspective includes the Data Source Explorer and Object Viewer. The Object Viewer provides more detailed information about the objects selected in the Data Source Explorer. The toolbar and menus include options and shortcut buttons to dialogs and wizards to help the user create and administer database objects.

The Data Transfer perspective provides support for transferring data and objects in Teradata and Aster Databases, and Hadoop systems. The Data Transfer perspective includes the Data Source Explorer, Transfer View, Teradata Progress View, and Transfer History View. The Transfer View provides a drag and drop palatte for copying table objects between Teradata and Hadoop systems and copying all objects between Teradata systems. The Progress View shows the status of active data transfer jobs. When the data transfer job completes, an entry is stored in the Transfer History View.

Modular Display

As mentioned above, within each of the Studio perspectives are views that provide the modular display for the perspective.

The Data Source Explorer View panel contains the database object tree display. It is here that you can create connection profiles to your Teradata Database, Aster Database, or Hadoop systems and interact with the database objects.

The Project Explorer View panel provides a hierarchical view of the Projects and their resource files It is here that you can select SQL files for editing or create new SQL files.

The SQL Editor is displayed when a SQL file is opened. Initially, the SQL Editor is opened to provide an area to enter SQL statements. The user must provide a connection profile in order to execute the SQL statements. Double clicking on a file in the Project Explorer will cause the file to be opened in the SQL Editor View.

The Teradata SQL History contains the history information when executing SQL statements and running database routines, user-defined functions, and triggers.

The Object Viewer displays detailed information about database object. Click the Object Viewer so that it is in focus. Then select an object from the Data Source Explorer and the detailed information about that object is displayed in the Object Viewer.

The Teradata Result Set Viewer displays the result set data. Individual Result Set tabs are created for each result set. The Result Set Viewer also contains a toolbar with actions that can occur on the result set data, such as saving, exporting, or printing the result set data.

The Transfer View provides a mirror display of the Data Source Explorer object tree and used to drag and drop database tables or objects for copying from one system to another.

The Teradata Progress View provides a display of the active data transfer jobs.

The Transfer History View provides a display of the completed data transfer jobs.

Studio Toolbars

Teradata Studio contains a toolbar that provides buttons to allow quick access to dialogs for creating database objects or invoking functions that are used while creating and modifying SQL files.

Teradata Studio toolbar is divided into the following sections:

File Actions: The File Actions toolbar buttons are used when editing a SQL file. They include Save, SaveAs, Cut, Copy, Paste, Undo, Redo, Print, and Show Whitespace.

 

SQL Tools Toolbar — The SQL Tools toolbar buttons are used to perform actions on the SQL statements within the SQL Editor. They include Execute as Individual Statements, Execute as One Statement, Execute a Single Transaction (Aster Only), Explain, Format, Prompt for Notes, Code Assist Auto-activation. SELECT Statement and SHOW DDL(Teradata Only) are activated when a table is selected in the DSE.

Data Tools Toolbar — The Data Tools toolbar buttons provide actions that are performed on a database table, such as Show Row Count, Teradata Load, and Teradata Export. Teradata Load and Export are enabled for Teradata Connections only.

 

Artifact Maintenance Toolbar - The Artifact Maintenance toolbar buttons provide actions to Move Space from one database to another, Copy and Compare objects, Rename objects, Drop objects, and Delete Databases. These actions are enabled for Teradata Connections only.

 

Create/Modify Actions Toolbar — The Create/Modify Actions toolbar buttons provide actions to create or modify database objects, such as creating or modifying datgabases or users, creating tables, views, stored procedures, macros, triggers, and user defined types. These actions are enabled for Teradata Connections only. NOTE: User defined types are created in the SYSUDTLIB schema.

 

Security Toolbar — The Security toolbar buttons provide actions to administer Profiles and Roles, and grant and revoke Rights and Privileges. Administer Profiles, Roles, Logon Rights, and Connect Through Rights is activated from the Database node at the top of the Data Source Explorer tree. Other  rights and privileges are activated from the specific object affected by the rights or privileges. These actions are enabled for Teradata Connections only.

 

Find Actions Toolbar - The Find Actions toolbar provides quick access to the Find Object and Find Next Object. These actions are enabled for Teradata Connections only.

 

Navigation Toolbars — The Navigation toolbar buttons are used to reference locations within the SQL file. They include Next Annotation, Previous Annotation, and Last Edit Location.

A view can also contain its own toolbar and drop down menu. These toolbar buttons and menu items provide actions on the data managed by the view. Included in the view toolbar are buttons to minimize, maximize, and restore the view. Maximizing the view will cause the view to take over the entire Teradata Studio window display. Click the Restore button to return the view back to its previous display.

Customize the Display

You can customize the look and feel of Teradata Studio by moving view panels within the main display window. A view can be moved by selecting the view and dragging it to a new location. As you move the view over the display, the mouse pointer will change depending on where you want to drop or dock the view. You can also drag the view outside the display area. The view will then become a "detached" view. You can also remove a view panel by clicking the "X" on the view tab. A view can be re-displayed by selecting the view from the Window>Show View option in the main menu. Or to return the perspective and views to their original display, select the perspective, then click Window>Reset Perspective...

You can also customize the Toolbars, Menus, and Command Groups of the display. Choose the Customize Perspecive... option from the Window menu.

The Customize Perspective dialog is presented for you to choose the Toolbar buttons, Menu options, or Command Groups you would like to change. Un-select the buttons or options so that they are not shown in the Teradata Studio's Administrator display.

Data Source Explorer View

The Data Source Explorer View panel contains the database object tree display. It is here that you can create connection profiles to your Teradata Database, Aster Database, or Hadoop systems and interact with the database objects. The Data Source Explorer view provides a hierarchical view of Teradata Database objects, nesting child databases and users within the parent database or user. Preferences are provided that allow you to choose which objects to load and display in the Data Source Explorer.

                  

Creating Connections

You can create connections to your database using the Connection Profile Wizard. The wizard is invoked from the Data Source Explorer by right clicking on the Database Connections folder or selecting the 'New Connection Profile' button, , from the Data Source Explorer toolbar.

          

Teradata Studio provides an option to create connection profiles for additional database servers other than Teradata.  You must provide the specific database server JDBC drivers for databases other than Teradata or Aster Database.

           

Select Teradata Database from the Connection Profile Types, enter a Name and click Next.

            

The Connection Profile Wizard is based on a driver template that references an embedded Teradata JDBC driver. Enter the database server name, user name, password, and default database name into the wizard dialog screen. The Authentication Mechanism allows you to choose an advanced logon mechanism, such as LDAP or Kerberos, or select the default mechanism, PASSWORD_PROTECTED. If you wish to save your password to disk, check the Save Password box. Otherwise, the password is stored in the profile and only active throughout the Teradata Studio session. When Teradata Studio is closed, the unsaved password is removed before the profile is written to disk. You will be prompted for the password the next time you connect to that profile.

Optionally, you can choose a different Teradata JDBC driver than the embedded Teradata JDBC driver. You can also add or remove the JDBC properties, as well as save the properties to an external file. The external file is called jdbcConnectionProperties.properties and located in the workspace .metadata/Teradata directory. The jdbcConnectionProperties.properties file allows you to share a set of JDBC properties with other Teradata Studio users. If the file exists when creating a new Teradata connection profile, it will load those property values into the list of JDBC connection properties. If the file exists but it is empty, the connection wizard will assume that no JDBC properties are specified and the Teradata JDBC driver will use the default settings.

You can also cache schema metadata, saving time when loading the database objects in the Data Source Explorer. Click the Cache Properties button to select schemas (or databases) to cache.

              

Aster Connection Profiles are created using a similar connection wizard with the embedded Aster JDBC Driver. Database server name, user name, password, port number, and database name fields are provided for user input. You can also cache Aster Database schema metadata to save time loading the Aster database objects in the Data Source Explorer.

Hadoop Connection Profiles are created using the WebHCat protocol to connect and discover database and tables information.

             

Creating Database Objects

You can easily create database objects in your Teradata Database using the Teradata Studio dialogs. First, switch to the Teradata Administrator perspective to access the Create and Administer Dialogs. The Dialogs are accessed from the Teradata Studio Tools toolbar or via the Data Source Explorer context menus. For example, to create a new Table, expand the Databases folder and locate the database you wish to create the table in. Right click on the Tables folder and select Teradata, then Create Table from the context menu.

The Create Table dialog will appear. First, enter your column information. Enter a column name and select the column type. The drop down list will present the list of valid column types for the Teradata version you are creating your table in. Click Apply to add the column to the list of columns. Click New to create another column definition. Next, choose the Primary Key, Indexes, and Foreign Keys for the table. Lastly, select the SQL Preview tab to view the generated SQL. Click Run SQL to execute the CREATE TABLE statement. This will create the table in the database and cause the Tables folder in the Data Source Explorer to be refreshed.

For additional help using a Teradata Studio dialog, clicking the question mark, , at the lower lefthand corner to open the Help context for the dialog.

Creating a SQL Statement (SQL Editor)

When Teradata Studio is launched, a SQL Editor area is provided for you to enter your SQL statements. First switch to the Query Development perspective. Once you have a connection to your Teradata or Aster database, you can begin to enter SQL statements in the SQL Editor window.  Click the Save button to save the SQL Editor to a file in the workspace or Export to export the file to the desktop file system.

           

Another option to create a SQL file is through the Data Source Explorer. Within the Data Source Explorer, select your database connection and click the SQL Editor icon, , from the Data Source Explorer toolbar. This will create a SQL file in the SQL Editor with the name 'SQL Editor [n]' and the connection profile set to your database connection. You are now ready to enter your SQL statement. 

You can also open an existing SQL file, located in the Project Explorer, into the SQL Editor and associate it with a connection profile. SQL files can be imported into the Project Explorer from your local desktop file system. Right click on the SQL project and choose the Import menu option.

               

The SQL Editor provides a scratchpad for you to enter your SQL statements. As an option, you can enable the auto activation of code assist by clicking the  toolbar button. If this option is enabled, as you type your SQL statement, code assist will pop up annotations showing a list of expected keywords. If a database name is entered followed by a dot, the content assist will display the list of tables from your database for you to select from. (Note: By default, auto activation of code assist is disabled. Also, you must select a Teradata or Aster Database connection profile type in order for SQL code assist to work.)

Code assist will also provide a list of SQL Templates. At the start of the SQL statement, hit the Cntrl+SPACE keys and a pop up list of templates is displayed. Scroll down until you find the template you want and double click on it to insert the template into your SQL Editor file. Anchor fields are provided that you can navigate by tabbing. You can also edit or add your own SQL Templates via the SQL Editor Preferences page.

Parameterized queries can also be created in the SQL Editor. The query contains parameters indicated by question marks. When the query is executed, the user is prompted for the parameter value(s) in the Configure Parameters dialog. Named parameters (appending backslash ,'\',<parameter name>) allows the user to specify a name for the parameter. When the Configure Parameters dialog is presented, the parameter names will be used to reference the parameters.

           

 

          

The SQL Editor also provides syntax coloring for your SQL statements. You can change the colors of comments, keywords, identifiers, types, or other syntax items via the SQL Editor Preferences page.

When right clicking in the SQL Editor window, a SQL Editor Context menu appears with options to execute the SQL statement(s) in your SQL file.

                 

The following options are presented:

  • Execute all of the SQL statements
  • Execute the selected SQL statement
  • Execute the SQL statements as individual statements (with a commit occurring between statements)
  • Execute the selected statement as one statement
  • Execute the current statement where the cursor is located
  • Execute the SQL statements as a single transaction (Aster only)
  • Visual Query Builder (Teradata only)

You can also choose the Execute options from the SQL Editor or top level toolbar, , , .

Manual commit and rollback of the SQL Execution is also provided via SQL Editor toolbar options.

An Autocommit checkbox is provided in the SQL Editor to allow the user to toggle Autocommit on or off. By default, Autocommit is ON. If the option is turned off, then the Commit and Rollback options are enabled for the user to manually control the commit of their SQL statements to the database or rollback if an error occurs.

SQL Query Builder

Teradata Studio provides a graphical interface for creating SQL statements for Teradata, referred to as the SQL Query Builder. You can edit an existing statement using the SQL Query Builder by selecting the statement within the SQL Editor and choosing the ‘Edit in SQL Query Builder…’ menu option. (Refer to figure above).

    

In addition, you can open a SQL file in the SQL Query Builder via the Project Explorer menu item, Open With...>Teradata SQL Query Builder.

This option will open the SQL Query Builder inside the SQL Editor view. This allows you to drag and drop the table objects from the Data Source Explorer into the diagram area of the SQL Query Builder.

You can also add additional tables and table joins by right clicking in the SQL diagram area and select Add Table or Create Join options. When adding a table, a list of tables and views is presented for you to choose from. Click OK to save your SQL statement back to the SQL Editor.

Data Transfer

Teradata Studio supports Teradata's Unified Data Architecture (UDA) by providing access to Teradata, Aster, and Hadoop via a single client tool. The Data Transfer Wizard provides a single dialog for transfering data between Teradata, Aster, Hadoop, and the external file system.

                            

You 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 between Teradata databases and Hadoop systems.

          

For example, when choosing to transfer data from a Teradata table, the Data Transfer Wizard will provide options to transfer the data to various destinations, such as: exporting to an external file, transfering to another Teradata system or table, or transfering to Hadoop.

Extract and Load Data

The Data Source Explorer provides an option to extract and load data for Teradata and Aster tables using Load Data Wizard and Export Data Wizard. Large Teradata tables and files will use the JDBC FastLoad or FastExport option depending on the number of rows and column data types supported. Otherwise, the JDBC load batch interface is used, and as well for Aster tables. Right click on the table and select the option from the Data drop down context menu.

             

Selecting the Load Data... option invokes the Data Transfer Wizard. If you are not in the Data Transfer Perspective, you will be prompted to switch to the Data Transfer Perspective where the Teradata Progress View and Transfer History View are displayed.

                  

The Data Transfer Wizard will provide the list of sources for the table load. Choose the External File option to launch the Load Data Wizard.

                

The Load Data Wizard will prompt the user for the file to load and define the necessary file format needed to identify columns when loading data into the table. File format options include the column delimiter (comma, semicolon, space, tab, or vertical bar “|”) along with the character string delimiter (double quote, single quote, or none) and File Encoding. If data already exists in the table, the load data will append or replace the existing data. You can also indicate whether column labels are in the first row, as well as whether to lock the table during the load process.

              

Selecting the Export Data option invokes the Data Transfer Wizard with the list of destination options for exporting the data to. Choose the External File to launch the Export Data Wizard.

              

The Export Data Wizard prompts the user for similar information as the Load Data Wizard. Choose the Output File, File Type and File Options.

               

The status of the data load or export job is displayed in the Transfer Progress View. When the job has completed, an entry is placed in the Transfer History View. Refer to the section below regarding the Transfer History View.

Smart Loader

The Smart Loader feature allows the user to load a text delimited or Excel file into a Teradata or Aster table. The Smart Loader is invoked from the Tables folder within the destination database via the Data Transfer Wizard.

        

 

From the Data Transfer Wizard, choose the Source Type as External File (Smart Load) to launch the Smart Load Wizard.

        

 

Like the other load data utilities, the Smart Loader will prompt the user for the input file.

         

Next, the Smart Loader will scan the file to determine the "best" column types and present these to the user.

          

Clicking the ellipses button (...) provides an option to modify the column definition.

          

Next, the table DDL is presented. The user can choose the 'Show in Editor' option to save the table DDL to the SQL Editor and manually change the table definition. Otherwise, clicking Finish will execute the DDL statement and begin loading the data into the newly created table.

         

The status of the Smart Load job is displayed in the Transfer Progress View. When the job has completed, an entry is placed in the Transfer History View.

Transfer History View

The Transfer History View displays the information about the data transfer, such as the name (given by the Export, Load, or Copy wizards), timestamp, source and destination systems, status, duration, rows transfered (if known), note, and summary. This information is stored in an embedded Derby database. You can sort and filter the rows and columns, edit the name or note. The data transfer job can be re-executed by selecting the entry and pressing the Re-execute toolbar button. The output of the transfer data job is displayed by pressing the Job Output button.

Copy Object Wizard

The Copy Object Wizard allows you to copy Teradata database objects from one Teradata Database system to another. Click here to view the Copy Object Wizard article and read more about copying Teradata database objects.

Hadoop Transfer Wizard (aka Smart Loader for Hadoop)

As with the Teradata Copy Wizard, you can transfer tables between Teradata Databases and Hadoop Systems. And, as with the Teradata Copy Wizard, there are two ways to invoke the Hadoop Transfer Wizard. Click here to view the Smart Loader for Hadoop article and read more about transfering tables between Teradata and Hadoop.

Table Data Editor

The Table Data Editor provides an enhanced feature to edit tables within the Data Source Explorer for Teradata and Aster tables. The data in the editor is broken up into pages, which allows for efficiency in updating large tables. Along with the standard insert, update, and  delete, data filtering, sorting, and in-memory filtering are also supported. The user also has the option of exporting the data to Excel or Text files.  It may be advantageous to export the data before it is modified.

The Teradata Table Data Editor is accessed via the Teradata menu. Select the table in the Data Source Explorer and right click and choose the Data>Edit Data... option.

The Table Data Editor will present the current rows of data from the table in a table grid display within the SQL Editor. You can click on a cell in the table grid to modify the cell contents or add a new row by clicking on the <new row> entry. A toolbar contains navigation aids and action buttons to control the row displayed, number of rows per page, page controls, as well as Filter, Sort, and Refresh actions.

Column operations are provided to hide or resize columns, find, replace or show values.    

           

Row operations are provided to copy and paste row data, insert and delete rows, or mark rows for export.

            

Row background colors are used to indicate whether a row has been updated (rose), inserted (yellow), or deleted (grey strike-through). These colors can be changed, along with other Table Editor options in the Table Data Editor Preference Page.

           

Depending on the edit option, a SQL UPDATE, INSERT, or DELETE statement is created. SQL Preview toolbar button, , is provided to show the SQL commands that will be run. Click the 'Commit Changes to the Database' toolbar button, , to run the SQL and commit the changes. A status message is displayed to indicate the actions committed to the database.

Project Explorer View

The Project Explorer View panel provides a hierarchical view of the Projects and their resource files. It is here that you can select SQL files for editing or create new SQL files. SQL files can also be imported from or linked to your file system. When Teradata Studio is first installed, an initial project called 'SQL' is created for you. You can create additional projects using the New>Project... menu option.

               

Within the Project Explorer, you can also choose an option to compare two files. The Compare Option displays the two files side by side with buttons that allow you to jump from one difference to another or move changes from one file to another. This is very handy when comparing SQL files or result set data.

The Project Explorer also provides an option to execute one or more SQL files from list of files.

          

Result Set Viewer

The Result Set Viewer displays the result set or parameter data from executing SQL statements and running database routines, such as stored procedures, macros, user-defined functions, and triggers. The Result Set Viewer provides an enhanced display of the Result Set data. It displays the result sets as tabs within the Teradata Result Set Viewer, allowing the user to select rows or cells from the Result Set data table grid. The Result Set Viewer provides menu options to hide or show all columns, move and sort columns, find a value within the result set data, perform aggregate functions on selected numeric columns, filter column data, format cells, and copy cells. Select a row or cell and right click to display the menu options.

       

Multiple result sets can be displayed as tabs or in a side-by-side sash display.

Large Objects (LOBS) can also be displayed in the Result Set Viewer. When a query result is being processed that contains an LOB result column, a dialog appears for the user to specify where and how to store the LOB values on the file system.

    

A toolbar is also provided with options to rename the Result Set tab, show the SQL associated with the result set, switch the display between text and grid display, switch the display between tabs and side-by-side sash display, and save, export, and print result set data. SQL result data can also be saved to a file within your Project or exported to an external file in the file system.

If the Export or Export All option is chosen, the Export Result dialog is displayed. Select a file name, format, and export options. Then click the finish button to create the exported file. The Save option presents a similar dialog.

    

The following screen capture shows the result data with totals on integer columns as exported to an Excel file.

SQL History

The SQL History View provides an enhanced display of the SQL History information. As SQL statements are executed from the SQL Editor or functions are run from the Data Source Explorer, an entry is placed in the SQL History. The SQL History view displays the data in a grid format, allowing the user to select rows and cells. The SQL History provides extensive information about the SQL execution, such as execution elapsed time, DBMS time, and fetch time, database server, row count, parameter display for macros and stored procedures, SQL statement, and SQL statement type. It provides options to copy cells or rows, edit the 'Note' or SQL for the SQL History entry, search for result history data, and re-execute SQL statements. Choosing the 'Edit SQL' option will open a SQL Editor file with the selected history entry's SQL statement. This allows users to further fine tune their SQL statements.

The SQL History view also provides a toolbar menu with options to delete rows or all of the history entries, filter columns, format cells, and sort columns, The SQL History uses an embedded Derby Database to manage the SQL History entries.

               

Object Viewer

The Object Viewer contains more detailed information about the database objects. When in the Teradata Administrator perspective and an object is selected in the Data Source Explorer, it is automatically displayed in the Object Viewer. You can click on the tabs to display additional information on the database object.

 

Compare Objects

Teradata Studio provides a wizard to help you compare the DDL of two Teradata objects. First select the Query Development perspective. Then choose a Teradata database object in the Data Source Explorer, right click and choose Teradata>Compare With...

This will invoke the Compare Objects Wizard for you to choose the object to compare with. Select the connection profile and database. If you are comparing tables, macros, views, stored procedures, user-defined functions, user-defined types, or indexes, you will be prompted to select another object of the same type.

If you are comparing database or user objects, click Next to choose child objects that will also be generated for the comparison.

Click Finish to display the two objects in the Compare Editor. The Compare Editor will provide toolbar buttons to navigate differences between elements in the two windows.

Help

Help is provided by clicking on the Help>Help Contents in the main toolbar.

Conclusion

Teradata Studio provides a multi-platform, administration tool for supporting your Teradata Database. Dialogs are provided to guide the user through creating and administering database objects.

To get up and running with Teradata Studio use the Download links above or go to the Tools Download area, pick your OS and take a look at the README.

To ask questions or discuss issues, refer to the Teradata Studio Forum and post your question.

Discussion
padhia 11 comments Joined 06/10
20 Jul 2012

Is there an article available that compares functionalities of Teradata Studio, Teradata Studio Express and Eclipse Teradata plugin products? It appears to me that, they are all based on Eclipse, but instead of being available as modules to add needed functionality to a single Eclipse installation, they are three separate products.

fgrimmer 486 comments Joined 04/09
20 Jul 2012

No, but maybe we need one. :-) All of the products are built from the same code base, so functionality wise the features will all act the same. The main difference is that they are each targeted toward a different user and thus contain a different set of features. Teradata Studio Express is for the SQL users. It is intended to help users manage SQL and their result set data.

Teradata Studio is for administrative users. It includes the same features as Studio Express but also includes dialogs to help users create and manage their database objects, such as Schemas, Users, Tables, Views, Permissions, etc. Teradata Studio Express and Teradata Studio are built as Eclipse RCP so they are a single download and install.

Teradata Plugin for Eclipse includes all of the features including additional features for Java Development and XML Services. It is built as a plug-in and is installed into an existing Eclipse installation. You can install just the needed features (or modules) that you want with Teradata Plugin for Eclipse.

padhia 11 comments Joined 06/10
21 Jul 2012

Thanks for the clarification.

Yes, a short article that compares all Teradata tools (including Windows only tools such as SQL Assistant, TD Administrator and Eclipse based tools) will indeed be useful. Here are some comparison categories that I think will be helpful: targeted audience, capabilities/functionality, platforms supported (Windows/Linux), Teradata versions supported, needed prerequisites (native libraries or pure JDBC drivers etc).

yogeshDhole 1 comment Joined 08/12
10 Aug 2012

Copy keys and copying into excel is really annoying. I can't copy columns directly to excel. I need to export, save file and then view it. Additional steps. Also Ctrl+Insert workaround is not working. Why did they change it?

thomm 1 comment Joined 10/09
21 Aug 2012

To copy directly to Excel, go to preferences, Teradata Datatools Preferences, Result Set Viewer Preferences and change the Copy Column Delimiter from the default of Comma Separated to Tab Separated and it appears to work fine, at least in the Mac OSX version.

veehell 3 comments Joined 07/12
25 Aug 2012

I have the very same issue with 'date' format conversion. Thanks for the recommended solution. I will try to test new .ini file very next Monday. So far I found TD Studio very helpful and this 'conversion' error forced me to use SQL Assistant on a side.

cheers
-vh-

caleb 1 comment Joined 01/11
27 Aug 2012

Thank you for the solution you posted.

Gotta love JRE backwards compatibility.

ndbajde 3 comments Joined 09/06
10 Sep 2012

Is there a way to specify the Port Number when setting up the Connection Details?

JohnE

fgrimmer 486 comments Joined 04/09
10 Sep 2012

Yes, edit the connection profile's JDBC Properties to include DBS_PORT. The default port number for Teradata is 1025, but you can change it for the connection by setting this property. Right click on the connection profile and select the Propertes, then Teradata JDBC Connection Properties. Click Add, then select DBS_PORT from the drop down list of JDBC Properties. In the Property Value, Click to enter a port value. Click OK to enter the value and OK to set the property.

ndbajde 3 comments Joined 09/06
10 Sep 2012

Found it. DBS_PORT under JDBC Connection Properties

JohnE

jjudge 4 comments Joined 07/09
10 Sep 2012

Have you connected Studio to Aster. Do I just need the Aster JDBC driver?

fgrimmer 486 comments Joined 04/09
11 Sep 2012

We are currently targeting Aster support for our next release of Studio and Studio Express.

ahmadsky 1 comment Joined 09/12
16 Sep 2012

installing problem. teradata expree 13 requires 1.6 java -version i hv informatica which support only 1.5 java version how can i solve this problem

fgrimmer 486 comments Joined 04/09
17 Sep 2012

Your 1.5 java version application should let you run with java 1.6. Or you could launch from DOS and set the java path.

abhijitvyas 5 comments Joined 08/06
02 Nov 2012

could not see Teradata Analyst pack which includes TSET & Index Wizard on Mac OS X version of studio express

fgrimmer 486 comments Joined 04/09
02 Nov 2012

Studio Analyst Pack is not available yet.

fgrimmer 486 comments Joined 04/09
02 Nov 2012

@abhijit, In response to your question regarding the toolbar being grayed out. The toolbar buttons are enabled depending on the objects selected in the Data Source Explorer. So for example, if you select a schema in the Data Source Explorer, the Tools>Create and Modify options are enabled. You can also get to the the Create and Modify menus by right clicking on a schema object in the Data Source Explorer, then select the Teradata menu option.

skd2day 1 comment Joined 04/09
07 Nov 2012

Can you tell me when the next version of Teradata Studio will be released? Thank you.

Stephanie DeRousse

fgrimmer 486 comments Joined 04/09
07 Nov 2012

Teradata Studio 14.02 is targeted for January.

Roopalini 22 comments Joined 05/08
08 Nov 2012

For some reason the Teradata studio installed , has Fastload / Fastexport option disabled. Any reason , why those options are disabled?

fgrimmer 486 comments Joined 04/09
08 Nov 2012

Make sure you have selected a Teradata table in the Data Source Explorer, then choose the Data Tools top menu option, or right click on the table and choose the Data menu option to see the Teradata FastLoad and Teradata FastExport options.

chuengel 1 comment Joined 05/09
12 Nov 2012

Where can i change the workspace Path.
We have in the C:\user only some KB so i have tho set a other drive/path for the workspace.

fgrimmer 486 comments Joined 04/09
14 Nov 2012

You can change the workspace path in the shortcut to launch Teradata Studio. Append -data after the TeradataStudio.exe. This is described in the Release Definition pdf file, section "Changing the Workspace Directory Location". The release definition is located n the /doc directory of the Teradata Studio installation.

bs520147 12 comments Joined 04/12
07 Dec 2012

Hello. It's my first time I'm writing here. I have a doubt about Teradata Studio related to Teradata Data Lab:
'Teradata Studio provides data lab users with a smart load (a.k.a self-loading) capability available 4Q 2012.'.

Is this version available now? Thank you.

fgrimmer 486 comments Joined 04/09
09 Dec 2012

@bs530147, SmartLoad for Teradata Data Lab is provided in Studio 14.02, which is targeted for January 2013. Sorry for the delay.

Roopalini 22 comments Joined 05/08
18 Dec 2012

Hello,

Could you please tell me the functionality of Master password for secure storage? Why do we need this?

Thanks
Roopalini

fgrimmer 486 comments Joined 04/09
19 Dec 2012

Master password is used by Eclipse for its secure storage. If you have configured Teradata Meta Data Services support preference in Studio, it uses the Eclipse secure storage to store the password. There is a known problem that may be happening in Studio where the user is repeatedly prompted for the Master password. The problem is that we are missing a jar file in the Studio RCP. We have fixed this problem in our upcoming 14.02 release, targeted for release next month.

Ryan.Costello 7 comments Joined 03/11
20 Dec 2012

Francine, is there any documentation on how to use the Copy/Compare functionality of Teradata Studio? I'm interested in learning what it can do and how to use it, but I haven't been able to locate any kind of documentation on it, and I'm a little hesitant to start clicking things that could potentially copy objects without understanding it.

Roopalini 22 comments Joined 05/08
20 Dec 2012

Thanks for the info Francine. I have another issue now. When I try to browse the tables, I frequently get the Null Pointer exception error.
Thanks for the Info Francin. I have another issue now.

Teradata tab at bottom of studio does not change when selecting a new table. Instead a null pointer exception is presented.
<< Message: RE: Teradata Studio - Java Null Pointer Exceptions >>
Could you please give a solution for this?

Thanks
Roopalini

Ryan.Costello 7 comments Joined 03/11
20 Dec 2012

OK, I started playing with it a little more, and I think I understand how the copy functionality works, but I can't seem to make it handle more than one object at a time. I can drag multiple tables (for example) into a database on another system, but the copy window then only allows me to generate the copy DDL for one table at a time via the pull-down. Is there no way to have the Copy facility generate the DDL for ALL of the selected objects? If I'm trying to copy, say, 20+ tables, this becomes pretty tedious to keep generating the individual DDL, and it's actually easier to simply select the multiple tables in the DSE window, right-click, and hit "Generate DDL". The copy facility seems to actually be less efficient (unless I'm misunderstanding it, which is entirely possible).

fgrimmer 486 comments Joined 04/09
20 Dec 2012

@Ryan.Costello, To find out more information on the Copy/Compare, go to the Help>Help Contents. Open the book Teradata Studio>Teradata Administrator>Copy and Compare Database Objects.

The copy is intended as a single object copy, so yes, one at a time. Teradata has other tools (such as Teradata Data Mover) for copying multiple tables at a time. As you mention, if you want to generate the DDL for all the tables in a Schema, you could use the 'Generate DDL' menu option.

fgrimmer 486 comments Joined 04/09
20 Dec 2012

Roopalini, A Null Pointer Exception should not happen. Can you send me more information about what you were doing so we can recreate the problem here and fix it.

Ryan.Costello 7 comments Joined 03/11
20 Dec 2012

I'm getting the null pointer exception also. I also noticed what looks like a bug in the Generate DDL and Copy Object functionality. I have a macro that references a column called "ASSM_DED_AMT", and when the DDL gets generated (either via right-clicking and selecting "Generate DDL" or via the Copy Object windows), it splits that column into an "AS" statement: "AS SM_DED_AMT", which of course messes up the DDL. This does not happen from Teradata Administrator...

fgrimmer 486 comments Joined 04/09
20 Dec 2012

We have fixed the problem in Generate DDL in our upcoming (targeted for January) 14.02 release.

Do you have more details on the Null Pointer Exception?

Roopalini 22 comments Joined 05/08
20 Dec 2012

Francine - When I try to click on a table , to see the structure at the bottom, I sometimes get the error - "Runtime exception encountered while trying to display an object in the Teradata View"

See error log for more details

Reason : DTS0129 badly behaved view handler

Java.lang.NullPointer.Exception

This is exactly what I do.

When opening Teradata Studio, I navigate to:
•My database
•The schemas folder
•The schema I wish to explore
•Tables folder within the schema - Sometimes the null pointer exceptions start happening here as noted in the first screenshot below.
•A table within this folder
o A Null pointer exception is presented.
o The Teradata view at the bottom of the studio does not change. In cases where I successfully selected a table without an error, I get the table. Then the next table selection presents the error and this view still shows the original table as opposed to the one I’ve just selected

I am unable to figure the error log too , just to check , if the error log gives more details

fgrimmer 486 comments Joined 04/09
20 Dec 2012

The error log is located in your workspace directory, in /.workspace/Teradata/teradata.log. If you can send the stack from the Null Pointer. thanks.

fgrimmer 486 comments Joined 04/09
21 Dec 2012

@Roopalini, thank you for posting the stack trace information. Can you also post the rest of exception trace after the JDBCException at the bottom? I think there is more information that can help determine what the problem is.

fgrimmer 486 comments Joined 04/09
26 Dec 2012

@Roopalini, Thanks for the additional information. It looks like problem is occurring because you don't have SELECT permission to the DBC.Columns view. When displaying the table information in the Teradata View, we access the data dictionary information from the DBC views. We will look into resolving the NPE, but to display the table information you will need to be granted select permission on the DBC views.

Roopalini 22 comments Joined 05/08
26 Dec 2012

Hi Francine,

Our Teradata box is multitenant and hence we actually have XVIEWS enabled, so that one customer isn't able to view another csutomer's tables / views ect. After enabling XVIEWs, we are able to expand the tree, browse the schema , however sporadically we get the NPE error. Is it because, we enabled the XViews?

Thanks
Roopalini

fgrimmer 486 comments Joined 04/09
26 Dec 2012

If you have the ViewX or ViewsVX preference selected than we will use the X or VX views to obtain the detailed information. From the stack trace above, it refers to DBC.Columns so I will verify we are checking the preference correctly.

YHKim 2 comments Joined 06/09
26 Dec 2012

I am testing with Korean character with charset=ASCII. Those characters are double-byte character with CP949. I can't see the Korean character on "Result set viewer". Can I insert and retrive the Korean character with charset=ASCII ? The most Korean customer store and retrieve with CP949 (MS949) not UNICODE(UTF16) at the moment.

Roopalini 22 comments Joined 05/08
27 Dec 2012

Thanks Francine....aprreciate your help with this issue.

Roopalini 22 comments Joined 05/08
27 Dec 2012

I again double checked if the Xviews are enabled and they are enabled. the error occurs when I try double click on a database / table. When I click the + sign , it doesn't appear.

fgrimmer 486 comments Joined 04/09
27 Dec 2012

@Roopalini, Just to clarify, how are you enabling the XViews? Also, I noticed in the log a socket communication error to the database. Can you disconnect your connection profile and reconnect to Teradata. Also before doing so, delete your error log so we can have a fresh log. thanks.

Roopalini 22 comments Joined 05/08
28 Dec 2012

The XViews have been enabled from windows - Preferences - Teradata data tool preferences - enabled ViewX , ViewsVX. I disconnected , deleted the connection and the log file and created a new one. Strangely now I don't see that error now. I also don't see the new log also created in the path C:\Users\username\workspace-studio\.metadata\Teradata.

Chuckbert 35 comments Joined 07/09
02 Jan 2013

@YHKim, The CHARSET setting in the connection determines the way Teradata Studio communicates with the Teradata system. Korean characters can't be translated into ASCII characters so you'll need to specify one of the CHARSET values that Korean characters can be represented (UTF8 or UTF16, for example). If you've specified one of the UTF choices for the CHARSET setting, you should be able to retrieve the Korean characters and display them in the result set viewer.

Your reference to CP949 makes me think you are needing to have Teradata Studio read or write Korean characters to the file system. That code page specifies an encoding of the Korean characters when they're being written to a file. Teradata Studio lets you specify what encoding to use when it reads and writes files.

If you select the "Preferences" item in the "Windows" menu, you can expand the "General" entry in the list of preferences and select the "Workspace" entry. The preference page that is displayed has a section "Text file encoding" that lets you specify the encoding that is used for files. If Cp949 is not specified as the Default encoding, you should be able to select the "Other" field and enter "Cp949" as the encoding. This will direct Teradata Studio to use Cp949 when reading and writing text data to files.

fgrimmer 486 comments Joined 04/09
03 Jan 2013

Roopalini, Thank you for the additional information. We have found an issue that we are working on to resolve this.

Roopalini 22 comments Joined 05/08
03 Jan 2013

Thanks a lot for looking into this Francine. Just an additional Info - I have also enabled LOG = DEBUG option from JDBC connection properties.

Roopalini 22 comments Joined 05/08
09 Jan 2013

Hi Francine - There is another issue I have in TStudio. When I right click on a database and click 'Generate DDL' the DDL Creation puts database creation statement at end of script. Shouldn't the DB creation be at the beginning. When I use the generated script in Erwin, it throws an error saying that the database does not exist. Is that how Generate DDL works in Teradata Studio. Could you please clarify?

fgrimmer 486 comments Joined 04/09
09 Jan 2013

Roopalini, Yes, we are aware of this issue and have fixed the order in our 14.02 release, targeted for the end of this month.

Roopalini 22 comments Joined 05/08
10 Jan 2013

Thanks for the update Francine!

Roopalini 22 comments Joined 05/08
13 Jan 2013

Hi Francine, have a question. Not sure if I am missing to do something. When I make changes to any structure of the table, it does not get reflected in my current session. Everytime I am disconnecting and logging back in to see the change that I made to the table structure.Is there anything that I am missing to do ?? Thanks!!

Roopalini 22 comments Joined 05/08
14 Jan 2013

Hi Francine - There is another issue as well. When I try to right click on a table and do a load. The result set viewer breaks into 2 tabs. Left side shows the line item history and right side shows the detailed message as to how many records loaded if it succeeded or the error message , if it fails. However , when I carry a second load, the right hand side of the window loses the details of the first load and only shows the table name. I am unable to recall the results of prior loads in this session. Hope I am not confusing.

We have Xviews enabled in our enviornment. Are the two issues by any chance related to 'XVIEWS' being enabled.

Thanks again for looking into the issues and all the inputs provided.

fgrimmer 486 comments Joined 04/09
14 Jan 2013

@Roopalini, You first question about changes to tables, if you make changes to tables by execute SQL in the SQL Editor, you need to do a manual Refresh of the Tables folder in order to reflect those changes in the Data Source Explorer. If you make changes using our Dialogs, a refresh is automatically performed.

I will look into your second issue.

fgrimmer 486 comments Joined 04/09
15 Jan 2013

@Roopalini, The Data>Load option is from Eclipse. In our upcoming 14.02 release we are providing a Teradata Load and Extract feature that will load and extract data from Teradata tables, using Teradata FastLoad when appropriate. We are focusing our efforts on this new and improved feature that should be used instead of Eclipse's data load option.

bjteradata 11 comments Joined 11/11
16 Jan 2013

@fgrimmer

Is the 14.02 release still targeted for the end of January? Any specific date or just by the end of the month?

Roopalini 22 comments Joined 05/08
16 Jan 2013

Thanks for the update Francine.Much appreciated!! We'll wait for the 14.02 release.

fgrimmer 486 comments Joined 04/09
16 Jan 2013

The 14.02 release is targeted for January 31.

RSG 1 comment Joined 05/12
17 Jan 2013

Hello,

I am trying a very simple query on one of the tables:

SELECT * FROM DWH."Locator";

and I do get the following error:

DTS0905: Exception thrown while processing resuts.

java.util.FormatFlagsConversionMismatchException: Conversion = s, Flags = #"

The same problem occurs if I try to show the "Sample Contents" for the data directly from the table. Curiously enough, if I "Edit" the data, it works without a hitch.

This does NOT occur for any other table, so it's perhaps because of the "Locator" name. However, somebody else in the company, who has also TD Studio installed, can execute the query without any problems.

Any ideas?

bjteradata 11 comments Joined 11/11
17 Jan 2013

@fgrimmer

Thanks!

Roopalini 22 comments Joined 05/08
17 Jan 2013

Hi Francine - There is another issue that one of the user is facing. When the user tries to execute multiple statements in the Teradata Studio by right clicking and selecting 'Execute as Individual statements'. It just does not create a history entry, however the history entry is created when he right clicks and selects 'Execute as single statement'. The other thing is we tried enabling LOG = DEBUG to capture any logs , when the history entry is not created. Strangely the logs are also not created. Could this be due to some preference (History not getting saved when multiple statements are highlighted and executed as individual statements)? Can you clarify ?

Thanks
Roopalini

fgrimmer 486 comments Joined 04/09
17 Jan 2013

@Roopalini, Execute as Individual statements will create an entry in the SQL History. What type of statement are you executing? New entries appear at the top of the table. Is a filter set to filter it out? Setting LOG=DEBUG as a JDBC Property will turn debug logging on for the JDBC Driver. If you want to turn on debug logging for Teradata Studio, follow the instructions in the Help. From the top level tool bar, choose Help>Help Content. Open the Teradata Studio help book and go to Troubleshooting. You don't need to add any of the components to the list, just set the Datatools logging level to DEBUG and Console Display Logging Filter to DEBUG. Also open the Console View and set to Teradata Log Console to see the output.

Roopalini 22 comments Joined 05/08
17 Jan 2013

Thanks for the prompt response Francine!! The statements are simple select with a wrong column name. Could you let me know where the filter is set to filter it out?
I shall have the user enable the debug and check if we are able to nail down the issue
Thanks
Roopalini

Chuckbert 35 comments Joined 07/09
18 Jan 2013

@RSG, the error you're seeing is a result of some code that works with Java 6 but fails in the way you're seeing with Java 7. The problem occurs when displaying TIME or TIMESTAMP results of a query.

Until the next version of the program is released, about the only way around the problem is running with Java version 6.

fgrimmer 486 comments Joined 04/09
21 Jan 2013

@Roopalini, a 'select of the wrong column name' would fail and this also would be displayed in the SQl History, even if you had a filter set.

Ryan.Costello 7 comments Joined 03/11
31 Jan 2013

Is 14.02 still expected to be released today?

fgrimmer 486 comments Joined 04/09
31 Jan 2013

I am sorry to say that there is a delay in the release of Studio 14.02. Current target is 1st quarter 2013. We are working hard to get it out as soon as possible.

bjteradata 11 comments Joined 11/11
01 Feb 2013

"fgrimmer
21 hours ago
I am sorry to say that there is a delay in the release of Studio 14.02. Current target is 1st quarter 2013. We are working hard to get it out as soon as possible."

I was looking forward to the updates. Oh well, at least it isn't last quarter or something like that.

rahul.gadodia 4 comments Joined 12/09
06 Feb 2013

Is there any feature in teradata studio that let me generate DDL's for procedure in separate script file so i can version control the DDL of the procedure easily

fgrimmer 486 comments Joined 04/09
06 Feb 2013

@rahul.gadodia, Teradata Studio does have a Generate DDL option. If you right click on the procedure in the Data Source Explorer, choose the Generate DDL menu option. The second to last page of the Generate DDL wizard allows you to open the DDL in a file. You can then save the file for version control.

rahul.gadodia 4 comments Joined 12/09
07 Feb 2013

I have hundred's of procedures. Can i select multiple procedures and then create separate script for individual procedures.so i want to create DDL script for procedures in separate sql script files.It would be very nice feature to have to maintain code control.Quest Toad has same kind of feature.

fgrimmer 486 comments Joined 04/09
07 Feb 2013

@rahul.gadidia, Currently you can select multiple procedures and choose Generate DDL but it puts them all in one file. We will look into adding an option to create one per file.

rahul.gadodia 4 comments Joined 12/09
08 Feb 2013

Thanks. It will be great feature to help with code development

fgrimmer 486 comments Joined 04/09
18 Feb 2013

Teradata Studio 14.02 is now available for Download, http://downloads.teradata.com/download/tools/teradata-studio

em186001 2 comments Joined 05/10
18 Feb 2013

Are there options to enable/disable admin features in this new version (14.02) of Studio? Also, can you limit or remove connection profile types to different databases?

em186001 2 comments Joined 05/10
18 Feb 2013

Is there a way to define connection profiles from the tool during the setup process? SQLA has a specific location you can put a configuration file to define .net data sources for all user.

gozillasnack 1 comment Joined 05/12
18 Feb 2013

I like this product a lot, but is there any way the execution plan of queries can be formatted to make it easier to read similar to SQL Assistant? Right now you can toggle between text and grid, but it's a lot more work to try to read the execution plan when it's not formatted. I have to use SQL assistant when I want to see the execution plan for a query.

fgrimmer 486 comments Joined 04/09
18 Feb 2013

@em189001, There is not a way to remove database profile types from the list. There isn't really a way to disable the admin features. You can customize the Teradata Administrator Perspective and remove items from the toolbars and menus.

Also, you can import predefined connection profiles using the Import option of the Data Source Explorer toolbar or menu.

fgrimmer 486 comments Joined 04/09
18 Feb 2013

@gozillasnack, We are working on providing query analysis features for our next release, which includes Explain plan analysis.

Ryan.Costello 7 comments Joined 03/11
21 Feb 2013

Any word on when Studio Analyst Pack will be released?

Also, is there a way to view GRANT/REVOKE statements prior to executing them? Within Administrator, you can set it so that it always shows you the SQL in a separate window before execution. It looks like that's an option within Teradata Studio for things like granting logon rights (there's a 'SQL Preview' tab), but not for granting ID and role permissions... I don't always want to execute these types of grants from the tool, but would be interested in having this tool generate the statement for me so that I can put it in a script.

fgrimmer 486 comments Joined 04/09
21 Feb 2013

We have not seen a committed date for Studio Analyst Pack at this time. We hope to hear more soon.

We are looking in to providing a SQL Preview option for the Privileges dialog.

bunch1962 5 comments Joined 09/12
12 Mar 2013

I had three questions about Teradata Studio:

  1. Is there a way to configure the query result set viewer to only display 1 result set?
  2. How can I hide 'Teradata SQL History'? Whenever I close it, it re-opens when I execute a query.
  3. How do I abort a running query? E.G. With Quest Toad, the 'Esc' key aborts a query. With SQL Server Management Studio, 'Alt' + 'Pause' aborts a query.

Thanks in advance.
Dave Bunch

Dave Bunch

fgrimmer 486 comments Joined 04/09
13 Mar 2013

Dave, Response to your questions:
1. Not currently. The result set viewer displays all result sets. Could you elaborate on what you are looking for it to do?
2. If you close the Teradata SQL History view, it will not re-open unless there is an error in the execution of the SQL statement. You can also move the SQL History view to a different location within Studio or drag it outside of the Studio window.
3. To abort a running query, you can click the Cancel button in the SQL Statement popup window. Or you can open the Progress View and cancel it there. To open the Progress View, go to the top Window menu>Show View>Other...>Progress. Click OK.  You should see the SQL execution and click the red square button to cancel.

gmach 1 comment Joined 04/13
16 Apr 2013

I'm new to Teradata, and was first introduced to SQL Assistant which was a big change from SQL Server Management Studio, Oracle SQL Developer, and TOAD.  Recently I'm one of two people in my department who is looking at Teradata Studio, and I must say I like it much better than SQL Assistant as far as result sets and so forth (love the tabs!).  I can get used to Alt-X to run queries (what's up with no F5 for that?) However, there is one nagging question I haven't been able to figure out:
I'll run a quick query that I need to dump the results to Excel.  While I can use the export function to achieve my goal, it takes several steps.  I can select cells to copy and paste in Excel, but for the life of me I can't figure out how to get column headers.  All I get is the values in the cells, and I then have to hand type in the column headers.  Is there a setting somewhere that I've missed?

fgrimmer 486 comments Joined 04/09
16 Apr 2013

Currently there is not an option. We will look into getting this as an result set export option for out next release. Thanks

TomMcGrath 4 comments Joined 03/05
07 May 2013

When will Teradata Studio software packages be available via the Teradata At Your Service Client Downloads service?  Our company's information protection organization does not consider the Teradata Developers Exchange to be a trusted site from which to download software.

fgrimmer 486 comments Joined 04/09
07 May 2013

@TomMcGrath, This is something we are looking into.

SnakeDr 2 comments Joined 09/09
07 May 2013

I would appreciate having the hierarchical structure that's the default view as in Teradata Administrator.
I don't quite understand the logic of not including this feature; a negative in my view and will slow down the adoption process. All said, I like the product, would be better with that feature.

fgrimmer 486 comments Joined 04/09
07 May 2013

@SnakeDr, The product inherits a SQL model that did not support the hierarchy. We have fixed this problem in our 14.10 release that is planned for Q3.

br230015 5 comments Joined 09/11
16 May 2013

Hi,
I have the latest Teradata Studio but some time unable to get results/rows when executing the query from Teradata Studio while the same query if run from SQL Assistant returns rows/results, Can you help me why it happening?
 
2nd question, unable to copy column heading in the results to excel, if save teh results as excel fime than it have column name as well, will appreciate any help
 
Badshah Rehman

Teradata

fgrimmer 486 comments Joined 04/09
16 May 2013

Badshah Rehman, One possibility on the returning result set is to look at the connection TMODE setting. With SQLA and ODBC, the default is set to TERADATA mode, where Teradata Studio sets the default to ANSI mode (as recommended by the Teradata JDBC driver). You can change the mode on your connection with Teradata Studio and see it that affects the returning result set.
If you Export or Save the result set to Excel, it will include column headers. The column headers are not currently included when copying cells from the result set. A new option (preference) has been added to our next release (14.10) to include column headers in the result set copy cells.

vadlal 1 comment Joined 05/13
17 May 2013

Hi,
I installed Teradata Studio v14.02 on my desktop(32bit). For some reason I cannot see Customize Perspective and Teradata Administrator under Window. Please help.

fgrimmer 486 comments Joined 04/09
19 May 2013

It sounds like a possible install error? Please make sure you have installed the 32-bit version of Teradata Studio 14.02 and have the 32-bit version of JVM, 1.6 or higher. You can open a topic on the Teradata Studio forum and post your teradata.log file for us to look at.

sondas 1 comment Joined 12/12
03 Jul 2013

Hi,
I have installed Teradata Studio in my 64bit win7 laptop. While create new connection I am getting ping failed error. 
Please help.

fgrimmer 486 comments Joined 04/09
03 Jul 2013

@sondas, There could be many reasons why the ping failed. The ping tries to get a connection to the database. You could have an incorrect user or password or database server. What is the detail message of the ping failure?

Ashwin4tera 17 comments Joined 11/11
22 Jul 2013

@fgrimmer Awesome Article..!
you have any user guide for Teradata Studio 14.02.
Can you share if  you have any download link.
Thank you.

fgrimmer 486 comments Joined 04/09
22 Jul 2013

@Sunnyguy4Tera, We don't have a separate User Guide document. This article and the embedded Quick Start Guide and Help books are the user guide documentation. There is also an article on DevX that describes the Teradata Studio's Smart Loader for Hadoop (http://developer.teradata.com/tools/articles/smart-loader-for-hadoop).

Ashwin4tera 17 comments Joined 11/11
23 Jul 2013

@fgrimmer Thank you.

streetjohns 1 comment Joined 09/09
02 Sep 2013

Is there a minimum spec of PC to get Studio to run effectivly?
 

fgrimmer 486 comments Joined 04/09
03 Sep 2013

The OS versions are listed in the Readme on the Download page. As for memory requirements, it will run with 2 GB but we recommend at least 4 GB.

gl186012 3 comments Joined 09/13
03 Sep 2013

Hello,is there some way to deal with the Chinese ? Like this 'È«Ê¡Ó¯ÀûÄ£¿é'.
UTF-8 and ASCII are all not useful.

Chuckbert 35 comments Joined 07/09
04 Sep 2013

@gs186012, In what way are you having trouble with Chinese? Database object names? Data in columns? Character set used in the connection with Teradata? What does "UTF-8 and ASCII are all not useful" mean?

gl186012 3 comments Joined 09/13
05 Sep 2013

Sorry, I am not clearly explaining this .  I connected Teradata with 'CHERSET=UTF-8' or ASCII , but when I  select * from tabe ,the data in columns of Chinese is like this 'È«Ê¡Ó¯ÀûÄ£¿é'. the right result need to be '你好'.
and I also modify the menu Window--Preference--General--Workspace Text file encoding from GBK to UTF-8,but is not useful.
Does the studio support Chinese code?
Thank u!
 

Chuckbert 35 comments Joined 07/09
05 Sep 2013

@gs186012, I've created a table with a column whose definition is VARCHAR(399) CHARACTER SET UNICODE CASESPECIFIC. When I connect with CHARSET=UTF8, I am able to store the '你好' characters into the column and display them in the  Result Set Viewer when I query the table.
I have a system where the Java installation does not include support for Chinese characters. When I query the table with Studio running on that system, the Chinese characters are displayed as boxes (Java's way of indicating that characters cannot be displayed). I can copy the data from the result set viewer and paste into an application that does have Chinese support and the correct characters are displayed.
If you have connected with CHARSET=ASCII and done any of the insert or query operations with the Chinese characters, the operation will either fail with a message saying there are untranslatable characters or will result in garbage (because the Chinese characters cannot be encoded in ASCII).
The column that you are putting the Chinese characters is defined with CHARACTER SET UNICODE, isn't it?
The Workspace Text file encoding preference will come into play only when the results are stored to a workspace file, not in the initial display in the Result Set View. If you store the results to a workspace file after setting the Workspace Text file encoding to a value that doesn't support Chinese characters, the resulting text file WILL contain garbage because the Chinese characters can't be represented in the chosen encoding. Is that what might be going on?

gl186012 3 comments Joined 09/13
11 Sep 2013

Thank u!
"The column that you are putting the Chinese characters is defined with CHARACTER SET UNICODE, isn't it?"
we use Latin when creat table. like this REGION_CODE CHAR(2) CHARACTER SET LATIN CASESPECIFIC TITLE '地市代码',
I connect the same DB with Teradata SQL Assistant (ASCII) , it's ok.
But when I use Studio connect with ASCII,it's not correct and if use Latin the software will alert 
Teradata JDBC Driver] [TeraJDBC 14.10.00.18] [Error 1011] [SQLState HY000] Session character set not supported by DBMS: LATIN1252_0A)
There is the different,is the Studio need to do something?

Chuckbert 35 comments Joined 07/09
13 Sep 2013

I've tried selecting LATIN1252_0A as my CHARSET value in the connection profile's JDBC Connection Properties and I get the Session character set not supported by DBMS message. I get a similar message when I try connecting with that session character set with BTEQ. The database system I'm using (and apparently yours) just doesn't support that value for the session character set.
Studio uses JDBC to connect to Teradata. Results provided by JDBC don't involve the TITLE clause of the column. That is a record reporting clause used by tools such as BTEQ. So the title value should not be a cause of problems in receiving results from that column.
If you set your connection profile's CHARSET to the default value of UTF8, what kinds of issues do you have. You certainly can't store the Chinese characters in the REGION_CODE column since it holds LATIN characters.

amentro 3 comments Joined 08/13
10 Oct 2013

Is there a Generate DDL option for Aster tables  / views ?

fgrimmer 486 comments Joined 04/09
11 Oct 2013

Not currently. We are working on this feature for our next relese.

amentro 3 comments Joined 08/13
23 Oct 2013

Is there a database/tables that can be queried to search for columns in tables, views, etc., as DBC is in Teradata ?

fgrimmer 486 comments Joined 04/09
23 Oct 2013

You can query the data dictionary views in DBC for this information. Refer to the Teradata documentation for more details on the data dictionary views. 

amentro 3 comments Joined 08/13
23 Oct 2013

re: DBC
sorrry, I meant to state that it is Aster tables, that I do not see a DBC for
Is there DBC for Aster too ?

fgrimmer 486 comments Joined 04/09
23 Oct 2013

Yes, Aster has similar views in the nc_system schema.

Ryan.Costello 7 comments Joined 03/11
23 Oct 2013

Hi Francine! Me again, with regards (again) to the Copy / Compare facility. I'm trying to use the Compare functionality now, but when I click on "Compare Definition Results" after dragging an object onto another, I get the following message:
 
"Teradata Browser Exception: User name has not been set in the dependencies preferences.
 
Please refer to the Teradata Dependency Browser Preferences to resolve this problem. Teradata Meta Data services may need to be configured to manage the referenced object"
If I click "OK" I then get this message:
* System(s) [AMEDWD, AMEDWP] do not have MDS enabled for Teradata Dependency Browser.
It does then display the differences, but I don't know why I'm getting that message. I found the Teradata Dependency Browser Preferences, and I see where I can enter information for Meta Data Services and User credentials, but I don't know what those are? I'm not at all familiar with MDS... How would I go about determining that? Or is it even necessary, considering it seems to be working despite the message in the notification window?

fgrimmer 486 comments Joined 04/09
23 Oct 2013

Ryan, The Dependency Browser is optional when comparing two objects. Having Teradata MDS enabled allows us to get the object dependencies from the MDS server. Otherwise we use the DTP SQL model to get the object dependencies. If you don't have access to MDS, then reset the values in the Dependencies Preference page.

tsalonia 2 comments Joined 09/13
06 Dec 2013

What are the valid values for TMODE, when editing the Properties of the Embedded JDBC Driver definition?  Is it possible to specify System Default, as in the ODBC driver?  We would like to set the default in the preferences so when all users install a scripted installation of Studio, the correct setting is already set.

fgrimmer 486 comments Joined 04/09
06 Dec 2013

@tsalonia, Current valid TMODE values are either ANSI, TERA, or DEFAULT.  You can set the value to DEFAULT and save your JDBC properties and share with other users to be their default. In the Connection Profile Wizard, there is a Save button that will create a jdbcConnectionProperties.properties file in your <workspace>/.metadata/Teradata directory. Others will place this file in their workspace  /.metadata/Teradata directory and it will use those default properties when creating their connection profiles

Anubeig 3 comments Joined 12/13
17 Dec 2013

Hi, Can you provide  Asterdata jdbc driver sample code. i.e connection string,how to connect etc...

fgrimmer 486 comments Joined 04/09
17 Dec 2013

@Anubeig, If you connecting to Aster from Teradata Studio, you would use the Connection Wizard and we will create the connection string for you. In the last screen of the connection wizard we display the connection URL that we have created.

Anubeig 3 comments Joined 12/13
17 Dec 2013

       

   Class.forName("com.asterdata.ncluster.Driver");

   String host = "10.80.166.110";

   String user = "beehive";

   String pass = "beehive";

       String aster = "jdbc:ncluster://" + host + ":8000/beehive";

            connection = DriverManager.getConnection(aster, user, pass);

      that you want to connect to in parameter 1 (in place of hyvm107)

            System.out.println("Successfully Connected to the Asteradata Database");

            String createTable = "create table t1(c1 integer, c2 varchar(100)DISTRIBUTE BY HASH(c1));";

 

Above code iam using to connect aster db from jdbc (I am running in windows 7 64-bit)

 

iam getting below error .........

 

java.sql.SQLException: [AsterData][NClusterJDBCDSII](34) : Database connection

roken ()

        at com.asterdata.ncluster.jdbc.core.NClusterConnection.connect(Unknown

ource)

        at com.simba.jdbc.BaseConnectionFactory.doConnect(Unknown Source)

        at com.simba.jdbc.AbstractDriver.connect(Unknown Source)

        at java.sql.DriverManager.getConnection(DriverManager.java:579)

        at java.sql.DriverManager.getConnection(DriverManager.java:221)

        at AsterJDBC.main(AsterJDBC.java:28)

Caused by: com.asterdata.ncluster.jdbc.core.MuleException: [AsterData][NCluster

DBCDSII](34) : Database connection broken ()

 

 

Could you please help me ..

fgrimmer 486 comments Joined 04/09
18 Dec 2013

What happens if you run the SQL from Studio? I was able to recreate your problem by entering a bad port number. The default port number is 2406. Are you able to obtain the connection successfully?

manoj_d 4 comments Joined 06/10
11 Mar 2014

Hi,
Facing error while installing Teradata Studio 14.10. on Citrix Server.
Error says:

Locking is not possible in the directory "S:\Program Files\Teradata\Client\14.10\Teradata Studio\configuration\org.eclipse.osgi". A common reason is that the file system of Runtime Environment does not support locking for that location. Please choose a different location, or disable file locking passing "-Dosgi.locking=none" as a VM argument.
S:\Program Files\Teradata\Client\14.10\Teradata Studio\configuration\org.eclipse.osgi\.manager\.fileTableLock(Access is denied).

Request to let me know if any one faced this error during installation and how the issue is resolved.
Thanks,
Manoj.
 

fgrimmer 486 comments Joined 04/09
12 Mar 2014

I do not have a Citrix platform to verify but I was pointed to the referenced response to the above problem:
Cause:

The error occurs when the user does not have the required permission to access the .fileTableLockfile. This file is in the configuration directory for Installation Manager.
The permission is not available because the umask settings for the previous user who ran Installation Manager were not set for group mode. The umask settings for the previous user did not allow files created in group mode to have group permissions equal to owner permissions.

The configuration folder is used to store OSGi cache information. The .fileTableLockfile is accessed by the OSGi cache at runtime. Failing to access the .fileTableLockfile can impact OSGi cache internal logic.
Resolving the problem:

To resolve this issue, take one of the following steps:

  • Change the permission for .fileTableLock file to 777
  • 777 777There are several directories that have .fileTableLock files that might require a change of permissions:
    • {IM_HOME}/eclipse/configuration/org.eclipse.osgi/.manager{IM_HOME}/eclipse/configuration/org.eclipse.core.runtime/.manager{IM_HOME}/eclipse/configuration/org.eclipse.core.runtime/.manager(Install location)/TeradataStudio/configuration/org.eclipse.core.runtime/.manager
    • {IM_HOME}/eclipse/configuration/org.eclipse.equinox.app/.manager(Install location)/TeradataStudio/configuration/org.eclipse.core.runtime/.manager(Install location)/TeradataStudio/configuration/org.eclipse.core.runtime/.manager(Install location)/TeradataStudio/configuration/org.eclipse.core.runtime/.manager(Install location)/TeradataStudio/configuration/org.eclipse.equinox.app/.manager
    • {IM_HOME}/eclipse/configuration/org.eclipse.core.runtime/.manager(Install location)/TeradataStudio/configuration/org.eclipse.osgi/.manager
  • Run this command on the configuration directory:

     chmod -R g+rwx
chmod -R g+rwx

  • As a root user, change the owning group for the contents of the root directory of the Teradata Studio configuration directory to the group that uses Installation Manager in group mode:
    chgrp -R <groupName> <{IM_HOME}/eclipse/configuration>chgrp -R <groupName> <{IM_HOME}/eclipse/configuration>

chgrp -R <groupname> <Iinstall location)/TeradataStudio/configuration>
chgrp -R <groupName> <{IM_HOME}/eclipse/configuration>
I hope this is helpful.

MH186045 1 comment Joined 03/13
13 Mar 2014

I would like to export the information in the tabs in the Teradata view.  Is there a way to select and copy the data or to export similar to with "Teradata Result Set Viewer"?

fgrimmer 486 comments Joined 04/09
13 Mar 2014

Michael, The information in the Teradata View is metadata we derive from the Data Dictionary. There is not a way to select and copy, except for some of the tab information such as the SQL for a Teradata Table. You can run queries against the Data Dictionary (DBC Views) to get the information into the Result Set Viewer.

manoj_d 4 comments Joined 06/10
17 Mar 2014

Hi Francine,
Thanks for your response on my previous post.
I am not successful in resolving another error (below) this time. This again is on Citrix which is a windows server.
Your response will be much helpful and appreciated.
Thanks,
Manoj.

!SESSION 2014-03-07 10:43:05.334 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 4 0 2014-03-07 10:43:07.475
!MESSAGE An error occurred while automatically activating bundle org.eclipse.core.resources (91).
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.core.resources.ResourcesPlugin.start() of bundle org.eclipse.core.resources.
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at com.teradata.datatools.util.Configuration.getConfigurationDirectory(Configuration.java:57)
    at com.teradata.datatools.util.logging.Activator.buildLogFileName(Activator.java:346)
    at com.teradata.datatools.util.logging.Activator.addLogFile(Activator.java:316)
    at com.teradata.datatools.util.logging.Activator.configureLog(Activator.java:293)
    at com.teradata.datatools.util.logging.Activator.start(Activator.java:82)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at com.teradata.studio.internal.ApplicationWorkbenchAdvisor.<init>(ApplicationWorkbenchAdvisor.java:64)
    at com.teradata.studio.StudioApplication.start(StudioApplication.java:34)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Caused by: java.lang.IllegalStateException: The platform metadata area could not be written: C:\workspace-studio\.metadata.  By default the platform writes its content
under the current working directory when the platform is launched.  Use the -data parameter to
specify a different content area for the platform.
    at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:61)
    at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:120)
    at org.eclipse.core.internal.runtime.InternalPlatform.getStateLocation(InternalPlatform.java:612)
    at org.eclipse.core.runtime.Plugin.getStateLocation(Plugin.java:313)
    at org.eclipse.core.internal.resources.LocalMetaArea.<init>(LocalMetaArea.java:57)
    at org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:430)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    ... 54 more
Root exception:
java.lang.IllegalStateException: The platform metadata area could not be written: C:\workspace-studio\.metadata.  By default the platform writes its content
under the current working directory when the platform is launched.  Use the -data parameter to
specify a different content area for the platform.
    at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:61)
    at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:120)
    at org.eclipse.core.internal.runtime.InternalPlatform.getStateLocation(InternalPlatform.java:612)
    at org.eclipse.core.runtime.Plugin.getStateLocation(Plugin.java:313)
    at org.eclipse.core.internal.resources.LocalMetaArea.<init>(LocalMetaArea.java:57)
    at org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:430)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at com.teradata.datatools.util.Configuration.getConfigurationDirectory(Configuration.java:57)
    at com.teradata.datatools.util.logging.Activator.buildLogFileName(Activator.java:346)
    at com.teradata.datatools.util.logging.Activator.addLogFile(Activator.java:316)
    at com.teradata.datatools.util.logging.Activator.configureLog(Activator.java:293)
    at com.teradata.datatools.util.logging.Activator.start(Activator.java:82)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at com.teradata.studio.internal.ApplicationWorkbenchAdvisor.<init>(ApplicationWorkbenchAdvisor.java:64)
    at com.teradata.studio.StudioApplication.start(StudioApplication.java:34)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

!ENTRY org.eclipse.osgi 4 0 2014-03-07 10:43:07.490
!MESSAGE An error occurred while automatically activating bundle com.teradata.datatools.util.logging (55).
!STACK 0
org.osgi.framework.BundleException: Exception in com.teradata.datatools.util.logging.Activator.start() of bundle com.teradata.datatools.util.logging.
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at com.teradata.studio.internal.ApplicationWorkbenchAdvisor.<init>(ApplicationWorkbenchAdvisor.java:64)
    at com.teradata.studio.StudioApplication.start(StudioApplication.java:34)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Caused by: java.lang.NoClassDefFoundError: org/eclipse/core/resources/ResourcesPlugin
    at com.teradata.datatools.util.Configuration.getConfigurationDirectory(Configuration.java:57)
    at com.teradata.datatools.util.logging.Activator.buildLogFileName(Activator.java:346)
    at com.teradata.datatools.util.logging.Activator.addLogFile(Activator.java:316)
    at com.teradata.datatools.util.logging.Activator.configureLog(Activator.java:293)
    at com.teradata.datatools.util.logging.Activator.start(Activator.java:82)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    ... 30 more
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.eclipse.core.resources (91).
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:122)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    ... 38 more
Caused by: org.osgi.framework.BundleException: Exception in org.eclipse.core.resources.ResourcesPlugin.start() of bundle org.eclipse.core.resources.
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    ... 48 more
Caused by: java.lang.IllegalStateException: The platform metadata area could not be written: C:\workspace-studio\.metadata.  By default the platform writes its content
under the current working directory when the platform is launched.  Use the -data parameter to
specify a different content area for the platform.
    at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:61)
    at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:120)
    at org.eclipse.core.internal.runtime.InternalPlatform.getStateLocation(InternalPlatform.java:612)
    at org.eclipse.core.runtime.Plugin.getStateLocation(Plugin.java:313)
    at org.eclipse.core.internal.resources.LocalMetaArea.<init>(LocalMetaArea.java:57)
    at org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:430)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    ... 54 more
Root exception:
java.lang.NoClassDefFoundError: org/eclipse/core/resources/ResourcesPlugin
    at com.teradata.datatools.util.Configuration.getConfigurationDirectory(Configuration.java:57)
    at com.teradata.datatools.util.logging.Activator.buildLogFileName(Activator.java:346)
    at com.teradata.datatools.util.logging.Activator.addLogFile(Activator.java:316)
    at com.teradata.datatools.util.logging.Activator.configureLog(Activator.java:293)
    at com.teradata.datatools.util.logging.Activator.start(Activator.java:82)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at com.teradata.studio.internal.ApplicationWorkbenchAdvisor.<init>(ApplicationWorkbenchAdvisor.java:64)
    at com.teradata.studio.StudioApplication.start(StudioApplication.java:34)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.eclipse.core.resources (91).
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:122)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    ... 38 more
Caused by: org.osgi.framework.BundleException: Exception in org.eclipse.core.resources.ResourcesPlugin.start() of bundle org.eclipse.core.resources.
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    ... 48 more
Caused by: java.lang.IllegalStateException: The platform metadata area could not be written: C:\workspace-studio\.metadata.  By default the platform writes its content
under the current working directory when the platform is launched.  Use the -data parameter to
specify a different content area for the platform.
    at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:61)
    at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:120)
    at org.eclipse.core.internal.runtime.InternalPlatform.getStateLocation(InternalPlatform.java:612)
    at org.eclipse.core.runtime.Plugin.getStateLocation(Plugin.java:313)
    at org.eclipse.core.internal.resources.LocalMetaArea.<init>(LocalMetaArea.java:57)
    at org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:430)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    ... 54 more

!ENTRY org.eclipse.osgi 4 0 2014-03-07 10:43:07.490
!MESSAGE Application error
!STACK 1
java.lang.NoClassDefFoundError: com/teradata/datatools/util/logging/LoggerFactory
    at com.teradata.studio.internal.ApplicationWorkbenchAdvisor.<init>(ApplicationWorkbenchAdvisor.java:64)
    at com.teradata.studio.StudioApplication.start(StudioApplication.java:34)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle com.teradata.datatools.util.logging (55).
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:122)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    ... 14 more
Caused by: org.osgi.framework.BundleException: Exception in com.teradata.datatools.util.logging.Activator.start() of bundle com.teradata.datatools.util.logging.
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    ... 24 more
Caused by: java.lang.NoClassDefFoundError: org/eclipse/core/resources/ResourcesPlugin
    at com.teradata.datatools.util.Configuration.getConfigurationDirectory(Configuration.java:57)
    at com.teradata.datatools.util.logging.Activator.buildLogFileName(Activator.java:346)
    at com.teradata.datatools.util.logging.Activator.addLogFile(Activator.java:316)
    at com.teradata.datatools.util.logging.Activator.configureLog(Activator.java:293)
    at com.teradata.datatools.util.logging.Activator.start(Activator.java:82)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    ... 30 more
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.eclipse.core.resources (91).
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:122)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    ... 38 more
Caused by: org.osgi.framework.BundleException: Exception in org.eclipse.core.resources.ResourcesPlugin.start() of bundle org.eclipse.core.resources.
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    ... 48 more
Caused by: java.lang.IllegalStateException: The platform metadata area could not be written: C:\workspace-studio\.metadata.  By default the platform writes its content
under the current working directory when the platform is launched.  Use the -data parameter to
specify a different content area for the platform.
    at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:61)
    at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:120)
    at org.eclipse.core.internal.runtime.InternalPlatform.getStateLocation(InternalPlatform.java:612)
    at org.eclipse.core.runtime.Plugin.getStateLocation(Plugin.java:313)
    at org.eclipse.core.internal.resources.LocalMetaArea.<init>(LocalMetaArea.java:57)
    at org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:430)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    ... 54 more

!ENTRY com.teradata.studiobase 4 0 2014-03-07 10:43:07.537
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Exception in com.teradata.studio.StudioActivator.stop() of bundle com.teradata.studiobase.
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:791)
    at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:565)
    at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1161)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:595)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215)
    at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284)
    at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:691)
    at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:598)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:390)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:198)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Caused by: java.lang.IllegalStateException: The platform metadata area could not be written: C:\workspace-studio\.metadata.  By default the platform writes its content
under the current working directory when the platform is launched.  Use the -data parameter to
specify a different content area for the platform.
    at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:61)
    at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:125)
    at org.eclipse.core.internal.preferences.InstancePreferences.getBaseLocation(InstancePreferences.java:44)
    at org.eclipse.core.internal.preferences.InstancePreferences.initializeChildren(InstancePreferences.java:199)
    at org.eclipse.core.internal.preferences.InstancePreferences.<init>(InstancePreferences.java:59)
    at org.eclipse.core.internal.preferences.InstancePreferences.internalCreate(InstancePreferences.java:209)
    at org.eclipse.core.internal.preferences.EclipsePreferences.create(EclipsePreferences.java:369)
    at org.eclipse.core.internal.preferences.EclipsePreferences.create(EclipsePreferences.java:357)
    at org.eclipse.core.internal.preferences.PreferencesService.createNode(PreferencesService.java:389)
    at org.eclipse.core.internal.preferences.RootPreferences.getChild(RootPreferences.java:63)
    at org.eclipse.core.internal.preferences.RootPreferences.getNode(RootPreferences.java:96)
    at org.eclipse.core.internal.preferences.RootPreferences.node(RootPreferences.java:85)
    at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.<init>(PreferenceForwarder.java:37)
    at org.eclipse.core.runtime.Plugin$1.run(Plugin.java:370)
    at org.eclipse.core.runtime.Plugin.getPluginPreferences(Plugin.java:373)
    at org.eclipse.core.runtime.Plugin.savePluginPreferences(Plugin.java:400)
    at org.eclipse.ui.plugin.AbstractUIPlugin.savePreferenceStore(AbstractUIPlugin.java:526)
    at org.eclipse.ui.plugin.AbstractUIPlugin.stop(AbstractUIPlugin.java:630)
    at com.teradata.studio.StudioActivator.stop(StudioActivator.java:53)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764)
    ... 18 more
Root exception:
java.lang.IllegalStateException: The platform metadata area could not be written: C:\workspace-studio\.metadata.  By default the platform writes its content
under the current working directory when the platform is launched.  Use the -data parameter to
specify a different content area for the platform.
    at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:61)
    at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:125)
    at org.eclipse.core.internal.preferences.InstancePreferences.getBaseLocation(InstancePreferences.java:44)
    at org.eclipse.core.internal.preferences.InstancePreferences.initializeChildren(InstancePreferences.java:199)
    at org.eclipse.core.internal.preferences.InstancePreferences.<init>(InstancePreferences.java:59)
    at org.eclipse.core.internal.preferences.InstancePreferences.internalCreate(InstancePreferences.java:209)
    at org.eclipse.core.internal.preferences.EclipsePreferences.create(EclipsePreferences.java:369)
    at org.eclipse.core.internal.preferences.EclipsePreferences.create(EclipsePreferences.java:357)
    at org.eclipse.core.internal.preferences.PreferencesService.createNode(PreferencesService.java:389)
    at org.eclipse.core.internal.preferences.RootPreferences.getChild(RootPreferences.java:63)
    at org.eclipse.core.internal.preferences.RootPreferences.getNode(RootPreferences.java:96)
    at org.eclipse.core.internal.preferences.RootPreferences.node(RootPreferences.java:85)
    at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.<init>(PreferenceForwarder.java:37)
    at org.eclipse.core.runtime.Plugin$1.run(Plugin.java:370)
    at org.eclipse.core.runtime.Plugin.getPluginPreferences(Plugin.java:373)
    at org.eclipse.core.runtime.Plugin.savePluginPreferences(Plugin.java:400)
    at org.eclipse.ui.plugin.AbstractUIPlugin.savePreferenceStore(AbstractUIPlugin.java:526)
    at org.eclipse.ui.plugin.AbstractUIPlugin.stop(AbstractUIPlugin.java:630)
    at com.teradata.studio.StudioActivator.stop(StudioActivator.java:53)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764)
    at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:565)
    at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1161)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:595)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215)
    at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284)
    at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:691)
    at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:598)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:390)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:198)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

fgrimmer 486 comments Joined 04/09
17 Mar 2014

This appears to also be a permission problem. When Teradata Studio is launched, it tries to create a workspace directory in the user's area. For example on Windows 7, it is C:/User/<USER>/workspace-studio. Try launching Teradata Studio with the -data option and specify a location to create the studio workspace.

bnett 2 comments Joined 11/07
19 Mar 2014

Francine,
I've just installed Teradata Studio 14.10 32-bit on a Windows 7 machine. Whenever I access the Grant/Revoke Permissions view, I am only seeing the databases in the top level of the hierarchy being selectable. The Data Source Explorer is showing the hierarchy just fine (great to see in V14.10), but if I mark a database deeper in the hierarchy and then go to Teradata->Grant/Revoke->Permissions, the database field is empty. Clicking on the pull-down menu just shows top level databases, as I mentioned.
Am I missing something?
Thanks!

fgrimmer 486 comments Joined 04/09
19 Mar 2014

Brian, This is a bug in the dialog. To workaround this issue, change the Data Source Explorer Load Preference to NOT show in hierarchical display (uncheck the box). We will work on resolving this problem. Sorry for the inconvenience.

manoj_d 4 comments Joined 06/10
19 Mar 2014

Thanks Francine.
Any idea where should we give this command (Try launching Teradata Studio with the -data option) on a windows environment.

fgrimmer 486 comments Joined 04/09
19 Mar 2014

Manoj, The -data is a command line option. Open a DOS window and locate the executable (TeradataStudio.exe) or you can add it to the desktop shortcut. So for example via DOS:
C: cd "Program Files (x86)"\Teradata\Client\14.10\Teradata Studio
C: TeradataStudio.exe -data c:\temp\newworkspace
 

manoj_d 4 comments Joined 06/10
24 Mar 2014

Thanks Francine. This worked for us.

JimHudd 1 comment Joined 11/11
08 May 2014

Hi, How can I see the return value from a stored proc? In SQLA the following would give me a result set but this doesn't seem to work in TD Studio 15.
call reset_password('jimbo',o1);
 
Regards,
Jim.

fgrimmer 486 comments Joined 04/09
08 May 2014

Jim, Execute the stored procedure from the Data Source Explorer's Run command. Locate the stored procedure in the Data Source Explorer, right click and choose the Run... option. It will prompt you for any parameters and execute the stored procedure, showing any output parameters in the result set viewer.

fgrimmer 486 comments Joined 04/09
08 May 2014

Jim, Also, Windows XP is no longer a supported platform for Teradata Studio.

jessielin 4 comments Joined 07/12
13 May 2014

Hello there, I noticed on a box where there'are a lot of user and databases created, it's taking a LONG time to open up Create Table Wizard, Teradata Compare Object View, and Data Lab View. Sometime it hangs...Is there any way to changes some options, or other tricks, to make things run faster? Thank you!

fgrimmer 486 comments Joined 04/09
14 May 2014

Jessie, Yes. You can control what gets loaded for Databases and Users. Go to Window>Preferences>Teradata Datatools Preferences>Data Source Explorer Load Preferences. You can also uncheck the 'Show Databases and Users in Hierarchical Display'. This will prevent the delay when opening up the dialogs.

ab185101 1 comment Joined 10/11
26 May 2014

Is the "Compare With" feature available in the current release? Not able to see the option when I right click on the table. Tried to serach for the Teradata Compare Object view as well. Did not find it.
Using Windows 64bit installation.
Teradata Studio Express
Version: 15.00.00.201404081510

fgrimmer 486 comments Joined 04/09
27 May 2014

Abhishek, Compare With is a Studio feature and not available in Studio Express.

karthikcts 2 comments Joined 03/14
27 May 2014

I am looking for Teradata Studio 14:10 version, as the release 15:00 doesn't support windows xp. Please help me finding the page to download prior version of Teradata Studio

fgrimmer 486 comments Joined 04/09
28 May 2014

Karthik, Teradata Studio 14.10 is no longer available on the Developer Exchange. If you have access to the Teradata Patch Server, you can download it from there.

DannyChin 4 comments Joined 07/09
18 Jun 2014

Hi. I  am getting error DTS0129 Badly behaved viewhandler. Is the solution enable XViews from windows - Preferences - Teradata data tool preferences - enabled ViewX?
 

fgrimmer 486 comments Joined 04/09
18 Jun 2014

Danny, What version of Studio are you running? What were you doing when you get the error message?

DannyChin 4 comments Joined 07/09
18 Jun 2014

Studio 14.02. I encountered the error when double clicked on schemas. The error is
An internal error occurred during: "Loading Core provider".

java.lang.Long cannot be cast to java.lang.Integer

DannyChin 4 comments Joined 07/09
18 Jun 2014

Studio version 14.02.0.201302060329

fgrimmer 486 comments Joined 04/09
18 Jun 2014

Danny, This problem has been resolved in later versions of Studio. Please download the latest version from the Developer Exchange Download site: http://downloads.teradata.com/download

DannyChin 4 comments Joined 07/09
18 Jun 2014

Looks like version 15.00 fixed the problem. Thanks!

islamfarouk 1 comment Joined 03/14
24 Jun 2014

Hi fgrimmer, please help me with this, when I use the content assist to autocomplete table name the only availble database is the parent database so I can't autocomplete any table of a child database.

fgrimmer 486 comments Joined 04/09
24 Jun 2014

Islam, The content assist reflects what is loaded in the DSE. By default Studio shows the DSE tree in hierarchical view, nesting child databases and users under parent nodes. You can change the display to flat by going to the Window>Preferences>Teradata Datatools Preferences>Data Source Explorer Load> uncheck 'Show Databases and Users in Hierarchical Display'. This should then show the full list in the content assist.

bmcclernan 3 comments Joined 04/08
27 Jun 2014

Hi Francine,
Is there a way to save a data load to a macro so that you can more easily repeat a load process?
 

Bill McClernan

fgrimmer 486 comments Joined 04/09
27 Jun 2014

Bill, Not quite sure how you would do that from a macro. But you can re-execute data loads from within Studio. After completing a data load (Data Transfer), an entry is placed in the Transfer History View. You can select the entry and press the ReExecute button. It will bring up the dialog and give you the option to replace or append the data.

bmcclernan 3 comments Joined 04/08
27 Jun 2014

Thanks, that should work!

Bill McClernan

Ashwin4tera 17 comments Joined 11/11
14 Jul 2014

Good article Thanks fgrimmer! We recently switched some of our business users from SQL assistant to Teradata Studio and I gave a demo to these users last week I got questions from users and I was not sure these features in Teradata Studio can you please answer these:

  1. Is there any max row limit to export results to a file?
  2. Any option to export results direct to the file without displaying on result set window.

Please update on this. Thank you.

fgrimmer 486 comments Joined 04/09
14 Jul 2014

Ashwin, 1) No, not from a result set. You can filter the data when exporting from a table. 2) We are working on providing this feature now. It will be available in our next release.

Ashwin4tera 17 comments Joined 11/11
14 Jul 2014

When can we expect the next release and what is the version number?
 
Thank you!

fgrimmer 486 comments Joined 04/09
14 Jul 2014

We are planning a 15.01.00 release by end of year.

Ashwin4tera 17 comments Joined 11/11
15 Jul 2014

Hi fgrimmer,
Our users are facing issue while executing Stored Procedure from Teradata studio here is error:
Failed [5510 : HY000] Invalid session mode for procedure execution.
Elapsed time = 00:00:00.000
My Question : Every time we need to change this Mode or Can we save couple of modes in properties? since user run variety of SQL's may have in different mode so changing the mode every time is hard right.
Please suggest on this.
Thanks.
 
 
 
 

Ashwin4tera 17 comments Joined 11/11
15 Jul 2014

Also Forget to mention:
Some of our users are highly experiencing stability / system freeze issues which make running queries very slow for them. This is on Windows XP OS.
What could be the issue and how can we resolve please suggest.
Thank you!

fgrimmer 486 comments Joined 04/09
15 Jul 2014

Ashwin, The error message 'Failed [5510 : HY000] Invalid session mode for procedure execution.' occurs because "the session mode within which the CALL SQL is submitted is different than the one in which the stored procedure was created. A stored procedure created in ANSI mode cannot be executed in Teradata mode and vice versa." You could have a separate connection profile with the session mode set differently for executing the stored procedure. But a connection profile can only have one TMODE property setting.
Can you provide more information about the system freeze issue? We have fixed some issues with canceling long running queries in our recent release.

Ashwin4tera 17 comments Joined 11/11
15 Jul 2014

Hi fgrimmer,
 
Hi fgrimmer,
The users are experiencing very long time to connect TD and loading schemas.
While expanding the schemas on left panel under Data Source Explorer when you click on SCHEMAS immediately getting freeze and taking long to get back from freeze. 
Please suggest on this.
Appreciate your quick Response.
Thanks.
 
 

fgrimmer 486 comments Joined 04/09
15 Jul 2014

Ashwin, What version of Teradata Studio are you running? In our latest version we have several different load options, which could speed up the display, such as load only users, or load only databases with perm space. If your database is unresponsive, you could cache databases (schemas) and also speed up the display.

Ashwin4tera 17 comments Joined 11/11
15 Jul 2014

We are using Version: 14.02.0.201302060329
 I sugested to use filter on schemas option is this different than Load only options?
Does this version has this load only option? I tried to use this cache option but this is bit hard since i can't use the filter if i use cache.
Please suggest.
 
Thanks.
 
 
 
 

fgrimmer 486 comments Joined 04/09
15 Jul 2014

Our current version is 15.00. We added the Data Source Explorer load options in 14.10. You can set a filter on the Schemas folder which will reduce the schemas loaded, either select just the schemas you want to load or filter out certain schemas.

Ashwin4tera 17 comments Joined 11/11
16 Jul 2014

Hi fgrimmer,
 
Thank you very much for your quick responce.
The user also experiencing system hangs very often w/ TD studio and connection taking very long time and for basic nevigation tasks in Teradata studio! 
Please suggest on this.
Thank you!

fgrimmer 486 comments Joined 04/09
16 Jul 2014

Is the Preference to use the ViewsVX set? If so, these views are much slower than the V views. YOu can check the Preferences>Teradata Datatools Preferences page. The default is to use the V Views. XV views are used to restrict showing objects the user does not have access to.
What are they doing when they experince system hangs?

Ashwin4tera 17 comments Joined 11/11
16 Jul 2014

The preference is not ViewsVX. We are using the default V Views is this faster than Views VX?
I have a meeting tomorrow i will get more updates from user and let you know what they are doing when system get hangs and other issues exactely what they are facing.
Thank you!

Ashwin4tera 17 comments Joined 11/11
17 Jul 2014

Hi fgrimmer,
I see the user is experiencing very slowness on almost all the tasks on his machine.
Like some basic task to load table list taking longer time and icons appearing very slow.
His machine is windows XP. I am running on Win 7 I don’t have this issues.
Could you please suggest on this.
 
Thank you.

fgrimmer 486 comments Joined 04/09
17 Jul 2014

Could it be their network connection or memory on the system?

Ashwin4tera 17 comments Joined 11/11
24 Jul 2014

Hi fgrimmer,
 
Yes looks like this is memory issue also planning to update the version.
 
Thank you very much this helps me a lot!

dm186044 2 comments Joined 08/14
1 month ago

I've installed TD Studio v14.10.01, and I want to work with 'Compare Objects' functionality.  Following the instructions on the page further up, upon right-clicking my database object in the Data Source Explorer, selecting Teradata, there is no "Compare with" option.  Any suggestions?
Thanks
Dan M.

Dan McCudden
Solution Architect
651-242-1775

Teradata
Analytic Data Platforms | Applications | Services
daniel.mccudden@teradata.com

fgrimmer 486 comments Joined 04/09
1 month ago

Dan, The 'Compare With' feature was introduced in version 15.00.

dm186044 2 comments Joined 08/14
1 month ago

Thanks, that explains why I couldn't find it. :-}

Dan McCudden
Solution Architect
651-242-1775

Teradata
Analytic Data Platforms | Applications | Services
daniel.mccudden@teradata.com

chillerm 3 comments Joined 04/11
3 weeks ago

I'm finally making the conversion over to Teradata Studio away from SQL Assistant :)  Thanks for the great article, and the explanations of various features.  We are trying to push Teradata Studio as the one tool to rule them all for our business and IT users, but one of the pushbacks we are getting is that you cannot load into Hadoop Directly from a flat file.  I was wondering if there were any plans in the future to add this functionality?  Essentially we want users to be able to use one tool to do any work in our multiple analytical environments.  
Thanks!
 

fgrimmer 486 comments Joined 04/09
3 weeks ago

Carl, Yes, this is something we are looking into.

gdamcn7 4 comments Joined 04/14
2 weeks ago

I recently started using the tool, and I think I found a bug in version 15.00. When I right click on a database and select "Generate DDL" and go through the wizard. In the last step it states "--DDL is not available" (with all defaults selected)
Guy

fgrimmer 486 comments Joined 04/09
2 weeks ago

Guy, It sounds like an error occurred trying to generate the DDL. Can you check the error log. They are located in the workspace directory in /.metadata/.log and /.metadata/Teradata/teradata.log.

gdamcn7 4 comments Joined 04/14
2 weeks ago

Hi Francine,
I went throught the steps again and retrieved the newly generated lines from the log:
2014-10-14 14:23:04,797 Teradata Datatools [main] INFO  com.teradata.studio - Teradata Studio Framework Version 15.0.0.201404081045
2014-10-14 14:23:24,746 Teradata Datatools [Worker-2] INFO  com.teradata.datatools.dtp.catalog - Provider: Extended Object Name support enabled value = true
2014-10-14 14:23:28,822 Teradata Datatools [Worker-2] INFO  com.teradata.datatools.dtp.catalog - DTS0001: Profile [tdn1pc01]- Kanji Enabled = false
2014-10-14 14:23:28,823 Teradata Datatools [Worker-2] INFO  com.teradata.datatools.dtp.catalog - DTS0041: Profile [tdn1pc01]- Extended Object Names Enabled = true
2014-10-14 14:23:58,634 Teradata Datatools [main] ERROR com.teradata.datatools.ddlgen.ui - null
I tried to generate the DDL for a database which has 5 child databases, which each have their own set of databases.

fgrimmer 486 comments Joined 04/09
2 weeks ago

Guy, Thanks for the log information. Can you also post any entries for that time period from the /.metadata/.log?

gdamcn7 4 comments Joined 04/14
2 weeks ago

Hello Francine,
Hereby the .log entries for the same timeframe:
!SESSION 2014-10-14 14:22:51.365 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_04
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.resources 2 10035 2014-10-14 14:22:55.628
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.ui.workbench 2 0 2014-10-14 14:23:00.433
!MESSAGE A handler conflict occurred.  This may disable some commands.
!SUBENTRY 1 org.eclipse.ui.workbench 2 0 2014-10-14 14:23:00.433
!MESSAGE Conflict for 'org.eclipse.ui.window.newEditor':
HandlerActivation(commandId=org.eclipse.ui.window.newEditor,
    handler=org.eclipse.ui.internal.handlers.NewEditorHandler,
    expression=,sourcePriority=0)
HandlerActivation(commandId=org.eclipse.ui.window.newEditor,
    handler=com.teradata.studio.administrator.handlers.DropHandler@572b90,
    expression=,sourcePriority=0)

!ENTRY org.eclipse.ui.navigator 2 0 2014-10-14 14:23:11.274
!MESSAGE Warning: popupMenuId of "org.eclipse.datatools.connectivity.DataSourceExplorerNavigator" was overridden: old value = "org.eclipse.datatools.connectivity.DataSourceExplorerNavigator.menu", new value = "org.eclipse.datatools.connectivity.DataSourceExplorerNavigator.menu".

!ENTRY org.eclipse.ui.navigator 2 0 2014-10-14 14:23:11.274
!MESSAGE Warning: popupMenuId of "org.eclipse.ui.navigator.ProjectExplorer" was overridden: old value = "org.eclipse.ui.navigator.ProjectExplorer#PopupMenu", new value = "org.eclipse.ui.navigator.ProjectExplorer#PopupMenu".
!SESSION 2014-10-14 14:28:06.076 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_04
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.resources 2 10035 2014-10-14 14:28:07.443
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.ui.workbench 2 0 2014-10-14 14:28:08.736
!MESSAGE A handler conflict occurred.  This may disable some commands.
!SUBENTRY 1 org.eclipse.ui.workbench 2 0 2014-10-14 14:28:08.736
!MESSAGE Conflict for 'org.eclipse.ui.window.newEditor':
HandlerActivation(commandId=org.eclipse.ui.window.newEditor,
    handler=com.teradata.studio.administrator.handlers.DropHandler@421103,
    expression=,sourcePriority=0)
HandlerActivation(commandId=org.eclipse.ui.window.newEditor,
    handler=org.eclipse.ui.internal.handlers.NewEditorHandler,
    expression=,sourcePriority=0)

!ENTRY org.eclipse.ui.navigator 2 0 2014-10-14 14:28:14.593
!MESSAGE Warning: popupMenuId of "org.eclipse.datatools.connectivity.DataSourceExplorerNavigator" was overridden: old value = "org.eclipse.datatools.connectivity.DataSourceExplorerNavigator.menu", new value = "org.eclipse.datatools.connectivity.DataSourceExplorerNavigator.menu".

!ENTRY org.eclipse.ui.navigator 2 0 2014-10-14 14:28:14.593
!MESSAGE Warning: popupMenuId of "org.eclipse.ui.navigator.ProjectExplorer" was overridden: old value = "org.eclipse.ui.navigator.ProjectExplorer#PopupMenu", new value = "org.eclipse.ui.navigator.ProjectExplorer#PopupMenu".
!SESSION 2014-10-15 09:01:12.516 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_04
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.resources 2 10035 2014-10-15 09:01:13.928
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.ui.workbench 2 0 2014-10-15 09:01:15.274
!MESSAGE A handler conflict occurred.  This may disable some commands.
!SUBENTRY 1 org.eclipse.ui.workbench 2 0 2014-10-15 09:01:15.274
!MESSAGE Conflict for 'org.eclipse.ui.window.newEditor':
HandlerActivation(commandId=org.eclipse.ui.window.newEditor,
    handler=org.eclipse.ui.internal.handlers.NewEditorHandler,
    expression=,sourcePriority=0)
HandlerActivation(commandId=org.eclipse.ui.window.newEditor,
    handler=com.teradata.studio.administrator.handlers.DropHandler@a3e5e,
    expression=,sourcePriority=0)

!ENTRY org.eclipse.ui.navigator 2 0 2014-10-15 09:01:21.696
!MESSAGE Warning: popupMenuId of "org.eclipse.datatools.connectivity.DataSourceExplorerNavigator" was overridden: old value = "org.eclipse.datatools.connectivity.DataSourceExplorerNavigator.menu", new value = "org.eclipse.datatools.connectivity.DataSourceExplorerNavigator.menu".

!ENTRY org.eclipse.ui.navigator 2 0 2014-10-15 09:01:21.698
!MESSAGE Warning: popupMenuId of "org.eclipse.ui.navigator.ProjectExplorer" was overridden: old value = "org.eclipse.ui.navigator.ProjectExplorer#PopupMenu", new value = "org.eclipse.ui.navigator.ProjectExplorer#PopupMenu".

tsalonia 2 comments Joined 09/13
1 week ago

Hello, I have a strange issue.  On the "Teradata SQL History" window, I've managed to resize the "Result" column under "SQL Summary" section, such that all the columns to the right of this one are no longer visible.  If I scroll all the way to the right side of Teradata SQL History, the last column visible is now the Result column.  There seems to still be the other columns present, because if I copy and paste the entire contents of SQL History, into Excel, all the columns are present.  Do you know of a way to resize the Result column back down to normal size, to allow the other columns to be visible again?

fgrimmer 486 comments Joined 04/09
6 days ago

Guy, Thank you for posting the logs. I don't see any exceptions logged. We will take a closer look as to why it could not generate the DDL. What happens if you change the Data Source Explorer Load Preferences to 'uncheck' the Show in hierarchical display option and try to Generate DDL again?

fgrimmer 486 comments Joined 04/09
6 days ago

Tony,  There is a preference file where we persist the column widths of the SQL History. If you delete this file, we will revert back to the default column widths.
First, close Teradata Studio. Next, locate the workspace for Teradata Studio, in your <USER> location, called workspace-studio. The preference file is called com.teradata.datatools.sqldev.history.prefs and located in /workspace-studio/.metadata/.plugins/org.eclipse.core.runtime/.settings
Delete the file called com.teradata.datatools.sqldev.history.prefs and restart Teradata Studio.

gdamcn7 4 comments Joined 04/14
15 hours ago

Hi Francine, when I switch to the non-hierarchical view the generation of DDL statements works, but it's not recurssing through the child databases. And this was exactly what we  wanted, for us it would be a way to backup the work we've done so if we would ever need to recreate the db tree from scratch we have the script for regenerating it.

isharma 1 comment Joined 06/12
12 hours ago

Hi Guy, your results indicate that the issue is most likely being caused by an object(s) in one of your child databases. We have an existing issue with some UDTs not generating DDL. Do you have UDTs within your child databases? What happens if you try to run Generate DDL on each of the child databases individually?

You must sign in to leave a comment.