TERADATA 15 FEATURES

·         Teradata  Database 15 offers new capabilities to empower analytic. 

·         Teradata QueryGrid, provides virtual compute capability within and beyond  the Teradata Unified Data Architecture, enabling companies to access and process analytic queries across multiple systems

·         Teradata Database 15, with QueryGrid, offers bi-directional data movement and push-down processing to open source Hadoop, and that the announcements develop its  unified data architecture approach to bridging the relational and non-relational technologies in the database market.

·         It minimizes data movement which takes time, and processes data where it resides.  It also reduces data duplication.

·         Teradata 15 will really open up the potential uses in data warehouse, including storing and analyzing sensor data along with other data stored on the Teradata platform.

JavaScript Object Notation:

JSON (JavaScript Object Notation) is new functionality to support the storage and processing of data into Teradata database.

• A JSON data type, its stores the data in JSON document or JSON records in relational format.
• JSON data can be used for all methods, functions, and procedures for processing, shredding, and publishing.
• The size of JSON documents up to 16MB
• JSONPath support provides simple traversal and regular expressions with wildcards to filter and navigate complex JSON documents.
• One of the advantages of processing JSON is the capability to perform query-on-reads, or late data binding, as opposed to the traditional early binding, or the query-on-write method used with traditional data types. With JSON, the database can actually discover what data is there when you run your query.

Teradata QueryGrid:

Hadoop  is an open-source framework that allows to store and process big data in a distributed environment across clusters of computers using simple programming models.

Teradata database now able to connect Hadoop with this QueryGrid so it’s called as Teradata Database-to-Hadoop also referred as Teradata-to-Hadoop connector.

·         Query  Grid  for Multiple System Analytics.

·         It provides a SQL interface for transferring data between Teradata Database and remote Hadoop hosts.

·         Import Hadoop data into a temporary or permanent Teradata table.

·         Export data from temporary or permanent Teradata tables into existing Hadoop tables.

·         Create or drop tables in Hadoop from Teradata Database.

·         Reference tables on the remote hosts in SELECT and INSERT statements.

·         Select Hadoop data for use with a business tool.

·         Select and join Hadoop data with data from independent data warehouses for analytical use.

XML Data Type:

·         Teradata also provides a new data type which stores and process the XML data.
It supports methods, functions, stored procedures for all operations like parsing, validation, transformations and Query.

·         The XML type stores values up to 2GB in size.

DBQL Show Parameters

A parameterized query used to place  parameters, and the parameter values are provided in a separate statement at time of execution. The main purpose is to  distinguishes between code and data. Also avoids attackers from changing the query by inserting SQL commands

Two  new Data Dictionary tables are

·         DBC.DBQLParamTbl

·         DBC.DBQLParamTbl logs

 Below  points are shows the overall enhancements in Teradata 15 release.

Performance

Light-Weight Redistribution

·         The Light-Weight Redistribution(LWR) also referred to as the Single Sender Redistribution (SSR). With this feature, the Teradata Database optimizer can switch from an all-AMP row redistribution to a few AMP row redistribution.

·         While executing the query, Teradata optimizer determines a query step is eligible for SSR, then the retrieved rows are redistributed by hash code to receiver AMP. In this case the number of AMPs is few. Without SSR all rows are normally redistributed across all AMPs.

·         Software Efficiency Improvements

Quality

·         New PI On Access Rights Table

·         DBQL - Show Parameters

·         Onsite System and Dump Analysis

DATA COMPRESSION

In addition to changing the internal data organization for the table, Teradata Columnar includes automatic dynamic com­pression and new compression mechanisms. Because all the data in a column storage container is for the same column, it is more consistent and lends itself to more compres­sion algorithms than row-oriented data. To take advantage of the consistency within the data, Teradata Columnar includes various compression mechanisms, such as:

• Dictionary
• Run length encoding
• NULL
• Trim leading or trailing bytes or characters
• Delta from mean
• UNICODE to UTF8

Teradata Columnar can apply multiple compression mechanisms to a column parti­tion. Applying this broad set of mechanisms to homogeneous data in columnar storage achieves dramatic compression rates.

GIVE THE HIGHEST PRIORITY TO IMPORTANT TACTICAL WORK

Everybody wants TO run queries ON your DATABASE AT the same TIME - FROM the boardroom TO the LOADING dock, FROM marketing TO front-line customer service - AND they ALL want answers AS CLOSE TO REAL-TIME AS possible. TERADATA WORKLOAD Management prioritizes the WORK AS per your specifications AND assigns resources TO make sure everything gets done ON TIME TO meet business demands. 

HASH JOIN ENHANCEMENTS

These enhancements extend the application of hash joins to include:

* Classical and dynamic hash outer joins

* Inclusion hash semi joins and exclusion hash semi joins

* Dynamic, inclusion, and exclusion hash semi joins with dynamic partition elimination

* Hash joins with cross terms

Benefits

* More efficient hash joins.

* Enhanced performance of outer joins, inclusion and exclusion semi joins, joins with

    partition elimination, and joins with cross terms.

Considerations :

Hash join enhancements with dynamic partition elimination only apply to dynamic hash

joins, inclusion hash joins, and exclusion hash joins. They do not apply to classical or

direct hash joins.

Indexes on UDT Columns

You can now create primary and secondary indexes on most types of user-defined type (UDT)columns

Benefits

You can declare a primary or secondary index on a UDT column when you create:

* Indexed tables

* Join indexes

* Hash indexes

* Secondary indexes

Considerations

* You cannot create primary or secondary indexes on:

* LOB UDTs

* ARRAY/VARRAY (Teradata internal UDT)

* The VARIANT_TYPE data type

ENCRYPTION ENHANCEMENTS

·         Teradata Database defaulted to a single set of encryption standards with no options for increasing encryption strength:

·         Teradata client applications provided the option to encrypt network traffic to and from the database, but all encryption used the default AES 128-bit algorithm.

THE QUERY WINDOW

SQL Assistant 15.0 uses a new code editor control to provide the Query window and SQL parsing functionality. This has required changes to the way in which some functions are performed, but has also added additional functionality.

The following changes will be observed:

• The scroll bars now conform to your chosen appearance settings
• Outline indicators now appear at the left of the SQL text
• The background colour of the current line may now be different from other lines
• A narrow yellow bar now appears at the left of any line that you have changed
• The bookmark symbols have changed
• Quick-Info tool tips may be displayed when you hover over a built-in function name
• Suggestion lists are now displayed for additional commands
• The Find and Replace dialogs have changed
• The process to Record, Play back, or manage, Keyboard macros has changed
• Changes during query execution

 Query Execution

·         When you execute a query only the portion that you are executing will become read only. This will allow you to continue working on other parts of the query without having to copy it to another Query tab.

·         You can now highlight and submit part of a Query for execution as an Import statement.

·         The approximate location of syntax errors is now indicated by red wavy lines below the text. These lines will remain until you next submit the query.
Note that syntax error locations are still only available when connected using Teradata.Net.