Teradata SQL Assistant
A new option has been added to the DB Tree page of the Options screen:
Display Triggers, Join Indexes, Materialized Views and UDTs
If you check this option a Triggers node will be added below each table and an Indexes node will be added below each database.
In addition, a User-Defined Types node will be added under the SysUDTLib database.
Note – The Indexes node will be called Materialized Views when connected to an Oracle system, or Materialized Query Tables when connected to DB2.
The Indexes node will display all Join and Hash Indexes in the database when it is expanded. Each item will display its name and the table[s] that it is defined on.
As with the Tables and Views nodes, if there are no objects of that type the Indexes, or Triggers, node will be removed when you attempt to expand it.
Earlier versions of SQL Assistant already provide additional information about some tables.
Global Temporary Tables will display a 'grey' icon and may be displayed in a different color [this is a user option]
Queue Tables will display a different icon [Only when connected using Teradata.Net]
Other enhancements in 14.10
When returning CLOB columns you can now specify the file encoding (UTF8, Unicode, ASCII) on the LOB Information dialog.
When exporting data to a Microsoft Access table you may now specify whether a Row Number column will be included in the output table.
When exporting data to a text file, or returning CLOBs, you may now specify whether a Byte Order Mark (BOM) is written at the start of the file.
If text you copy from Microsoft Word, Outlook, or other applications, contains 'Smart Quotes' these will be automatically converted to regular quotes when you paste the text into SQL Assistant. This will avoid syntax errors when you execute the Query.
We now support systems that have only Microsoft .Net Framework 4.0 or 4.5 installed. You will no longer be required to install Framework 2.0 in these cases.
Using Teradata.Net instead of ODBC
Microsoft's .Net Data Provider for ODBC was intended as a temporary way for applications to connect to a database through ODBC while the vendor had time to write a database specific .Net Data Provider for that database.
As a result of this Microsoft implemented only the bare minimum of ODBC functionality. This means that some data types are not fully supported and some areas of functionality are not supported at all. It strongly recommended that all users use Teradata.Net rather than ODBC when they connect to a Teradata data source.
Using Teradata.Net will provide the following additional or improved features:
Data retrieval may be up to 8 times faster
Data import may be up to 70 times faster
You may directly edit the data in a table using an editable grid
The approximate location of syntax errors will be highlighted after a query fails
Macros [or parallel query execution] that return no rows from one select but return rows from another select will work correctly
Time/Timestamp columns with fractional seconds or Time Zones will be displayed in full
Decimal values with more than 28 digits will display correctly
Returning Interval columns will not cause conflicts with certain other column types
CLOBs may be returned using any character set
Queue Tables will be displayed using a different icon in the database tree
All User Defined Functions will be displayed in the database tree
Note that the first time a user launches SQL Assistant 13.0 or higher the application will automatically create a DataSources.config file from the Teradata ODBC entries in their registry.
Additionally, a customer DBA or IT staff member may pre-create the Teradata.Net data sources by creating a DataSources.config file and including it as part of the install. This file can also be sent to users after performing a standard install.
This file may be installed either in the user's private branch or under the 'All Users' branch.
On Windows 7 the locations would be:
Adding support for an 'unsupported' database
SQL Assistant should work with any database that provides an ODBC interface. However the application needs to know a few things about that database in order to work correctly.
That database specific information is stored in a file called Vendors.config which is located in:
In general only a user with administrative rights will be able to change files in this path. Starting with SQL Assistant 18.104.22.168 the application will first look in the following directory:
If the file is found there then this version will be used. Administrative rights are not required to change files in this directory.
For additional information on adding support for a new vendor database please refer to the Vendors.config topic in Appendix C of the user guide.