Teradata Studio 14.10 is now available for download. Teradata Studio is an administration tool for creating and administering database objects. 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 to benefit from the many high quality Eclipse features available while focusing on value-add for the Teradata Database.
Aster Schema Cache
Schema caching provides a mechanism, which stores the selected schemas locally in the format of an XML file. The user is provided with an interface for selecting which schemas to cache. Caching allows for a quicker loading time in comparison to loading the schema from the database each time.
The DSE Tree Hierarchy provides an option to display the databases in the Data Source Explorer in a hierarchical format (the flat format option is still supported as well). This provides a clearer view of relationships between databases and users. This feature also provides a set of preferences to select what to load from the database and what to display in the Data Source Explorer.
The Teradata SQL Editor provides a mechanism that allows the user to write SQL statements and execute them against a database. The Teradata SQL Editor does not replace the open source SQL Editor but instead provides a more efficient and accessible method of performing the functions. The Teradata SQL Editor includes a connection indicator, a connection profile list, an execute menu, and a save menu.
The Table Data Editor provides an enhanced feature to edit tables within the Data Source Explorer. 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 to Excel or Text files.
The 14.10 database definition provides the XML data type in addition to existing types. Dialogs such as Create Table, Create Procedure, Create User-Defined Function, and Create UDT support the XML type for column, parameter, and return types. In the case of Java Stored Procedures and Java UDFs, the XML data type is not displayed as an option because it is not supported.
This release of Teradata Studio includes various interface enhancements. The Privileges dialog has been refactored to be consistent with other platform dialogs. The dialog has been organized into Display, Grant, and Revoke tabs and there is an 'All But' option, which allows the user to grant or revoke all privileges but the ones selected in the dialog.
The Generate DDL dialog has also been enhanced; options not supported by Teradata such as the user defined string terminator and running the DDL on a server have been removed.
Change Password dialog has been added to allow users to quickly change their password.
The Smart Loader for Teradata is now available outside of Teradata Data Lab. Users can invoke the Smart Loader by right clicking on the Tables folder for a Database and choose the Smart Load Data option.
Online Help can be accessed within Teradata Studio:
Reference Documentation can be found on the download page or at: www.info.teradata.com
Managing Roles in Teradata Studio 14.10?
In the GUI I can create a Role and assign users to that Role.
Where can I see which authorisations that are granted to a role?
How and where can I grant Select on a database to a Role? It seems that I only can grant Select/Insert/Update/Delete on objects within a database and not on Database level? I prefer to do it on database level to keep it simple.
Teradata Studio 14.10 doing unnecessary full table scan?
I'm right-clicking on a table and choosing data/Sample Contens. What I see in ViewPoint is a sql doing full table scan like "Select * from TableName;"
Since I'm asking for a Sample, shouldn't the SQL be: "Select * from TableName Sample nnn;" ?
This SQL will return back rows in a few seconds even on very large tables (and avoid tablescan)
Yes, but my point was: Is it possible the change this in future releases? I can't see anyone really want a full table scan when they ask for some sample rows.
A full table scan generated from many users will potentially kill the system.
Perhaps even the user could be prompted for how many rows he wants returned and thereby fire a SQL like "Select * from Table sample #numberofwantedrows" ?
Hi, I have questions regading new version of TD STudio 14.10:
Thank you very much!