Teradata Studio Express 14.00 (formerly Teradata SQL Assistant Java Edition) is now available for download. Teradata Studio Express is an information discovery tool for retrieving and displaying data from your Teradata Database systems. It can be run on multiple operating system platforms, such as Windows, Linux, and Mac OSX. It is built on top of the Eclipse Rich Client Platform (RCP) which allows Teradata Studio Express to benefit from the many high quality Eclipse features available while focusing on value-add for the Teradata Database.
Teradata Studio Express has replaced Teradata SQL Assistant Java Edition. Stay tuned for more information on future Teradata Studio Family product offerings.
Custom Attributes provides the ability for users to specify additional attributes for objects displayed in the Teradata View. When objects of the type are displayed in the Teradata View, additional tabs containing the attributes’ values will be provided. Single attributes or a collection of attributes are displayed in a table format.
The custom attributes are defined in an XML file that is located in the user's workspace .metadata/Teradata directory. The XML file contains information about the type of object, name, tooltip and icon for the Teradata View’s tab, and the query that will run to retrieve the object’s attributes.
History Cleanup Dialog
A Cleanup History dialog has been added to the Teradata SQL History toolbar to help the user clean up the history. The dialog allows the user to specify one or more criteria to match the rows that they wish to delete. They can also select an option to delete all duplicate queries. In order to be considered duplicate, both the data source and the SQL statement must be identical. In deleting duplicates, all except the most recently execute entry will be deleted. The Cleanup Dialog will also allow the user to compact the SQL History database. The compact feature works by freeing up unused allocated space.
This feature provides the option to import the SQL Assistant history in XML format. The Teradata SQL History import dialog now provides an option to import a SQL Assistant History (.xml) file.
Users have the option to provide a JDBC Property Configuration File that acts as the default list of JDBC properties when creating a new connection profile. The JDBC Property Configuration File is located in the user's workspace .metadata/Teradata directory and allows for deployment of Teradata Studio Express with a different set of JDBC properties. An empty JDBC Configuration File indicates that no JDBC properties will be set and connections will use the JDBC driver default values.
Log messages are now stored in the teradata.log file, located in the user's workspace .metadata/Teradata directory. There is also a Teradata Log console view, which can be used to display log messages. The logging levels of the two displays are independently controlled and can be set in Teradata Datatools Preferences page.
In previous releases, the Teradata Result Set Viewer was displayed inside the Teradata View. It has now been moved to its own view display, allowing users to view result sets at the same time as viewing database object information in the Teradata View. Additionally, the Result Set Viewer has added a toolbar button to allow users to rename result set tabs and made performance enhancements when displaying large result set data.
A new toolbar button, , has been added to the main, topmost toolbar that allows the user to toggle on the auto activation of code assist. Code assist provides drop down syntax suggestions as you pause while entering your SQL statement in the SQL Editor. This operation uses metadata from the database so for large databases the operation can take a long time. Code assist is turned off when Teradata Studio Express is initially installed. You can turn it on by clicking the Code Assist toggle button.
This feature provides the ability to hide tabs that are displayed in the Teradata View for database objects. Tabs that provide details of the database objects can be hidden by pressing the tab’s close button. Tabs that are hidden will not be displayed when objects of that type are later shown in the Teradata View. Hidden tabs can be restored by selecting the “Restore Tabs” button or menu item in the Teradata View’s toolbar.
A tab’s visibility can also be managed in the Teradata Datatools Preferences page. The Teradata View Object Visibility preference page displays a list of the Teradata View tabs whose visibility can be set. Tabs with their checkboxes checked will be shown in the Teradata View when appropriate. Tabs that are unchecked will not be displayed.
For more information on using Teradata Studio Express, refer to the article, Teradata Studio Express.