Teradata SQL Assistant Java Edition release 13.11 is now available for download. SQLA JE 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 SQL Assistant Java Edition to benefit from the many high quality Eclipse features available while focusing on value-add for the Teradata Database.
Passwords can expire. In many cases the original password is a temporary password and the user is expected to change it when logging on for the first time. It is now recognized when a password expires (SQL Warning error code: 3032) and the user is prompted for the new password. The connection is retried with the JDBC property ‘NEW_PASSWORD’ set to the new password and the new password is saved in the profile.
Execute SQL Files from the Project Explorer
This feature provides the ability to execute one or more SQL files from within the Project Explorer. The user can select the SQL file(s) and right click and choose the Execute Teradata SQL Files option. If multiple SQL files are selected, a dialog is displayed to confirm the connection profile for the SQL files. If a parameterized query is contained within the SQL files, the user is prompted for the parameter values.
This feature provides the ability to generate the Database EXPLAIN results from a SQL statement by pressing the F6 key or clicking the Explain icon, , in the toolbar. The EXPLAIN results are displayed in the Teradata View window.
This feature provides the ability to export and import the history information from the Teradata SQL History to an external file. This ability allows SQL statements, which are part of the SQL History, to be shared between installations of SQLA JE. New Export and Import menu items are provided as part of the Teradata SQL History View toolbar.
LOB support includes the ability to view LOBs within the Result Set Viewer, and include LOBs as parameters when running parameterized SQL. When a query result is being processed and a result column contains an LOB, a dialog appears. The dialog requests information about where the LOB values are to be stored on the file system, what the base name of the file is to be (initially the column’s name), what the file extension should be, whether the contents of image values are to be shown as images in the result set view, and whether image values are to be saved when the images are displayed in the result set view. When LOBs are needed for parameters to a SQL statement, the Configure Parameters dialog allows the user to specify the location of the LOB file.
This feature provides an option for users to manually enter a JDBC property and its value. This is useful when non-standard JDBC properties are required for the Teradata connection. In the drop down list of JDBC Properties, scroll down to the bottom and select the USER_ENTERED_PROPERTY option. A dialog appears for you to enter your JDBC property name and its value. The name/value pair is then stored and passed to the JDBC driver when creating a connection to the Teradata Database.
This feature provides a Row Count menu option when a table is selected from the Data Source Explorer. Select the table from the Data Source Explorer and click Data>Row Count. A dialog with the number of rows for the table appears.
The Schema Cache option allows the user to designate particular schemas (databases/users) to be cached. A schema cache file that contains the metadata for the schema is created. The metadata describes all of the information about the schema, such as its tables, columns, constraints, indexes, macros, parameters, stored procedures, user defined functions, user defined types, views, and so forth. The schema cache is associated with the connection profile. If the connection profile is deleted, so is the schema cache list and any schema cache files that were created. The schema cache files are stored in the workspace/metadata directory.
When the user first connects to the database and opens the Schemas folder, the schema cache file is created in a background job. Once the cache is created, if the user refreshes the list of schemas (by clicking the Refresh menu option on the Schemas folder), the cached schemas are loaded from the schema cache file. The schema is then highlighted within the Data Source Explorer with the cache icon, . Note that any modifications made to objects of a cached schema are not immediately reflected in the cache. The user must refresh the schema cache for those changes to take effect.
This feature allows you to create connection profiles for Oracle, IBM DB2, and SQL Server databases. Support is provided by the standard Eclipse Data Tools Platform functionality. Note that SQL result set data for other database connections is displayed in the SQL Results View instead of the Teradata View, used only for Teradata Database connections.
For more information on using Teradata SQL Assistant Java Edition, refer to the article, SQL Assistant Java Edition.
From where do I download SQLA JE? I donot see anything in downloads section or on T@YS site. Can someone please help.
Arnav, Teradata SQL Assistant does not run on the Mac OSX. You can download Studio Express for Mac OSX at: http://downloads.teradata.com/download/tools/teradata-studio-express