This post provides brief descriptions of the new features in this release in database level.
JavaScript Object Notation:
JSON (JavaScript Object Notation) is new functionality to support the storage and processing of data into Teradata database.
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.
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.
- 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.
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.
Sample Table creation
CREATE TABLE EMP_TABLE (
EMPID INTEGER,
EMPName VARCHAR(256),
EMPXML XML )
PRIMARY INDEX (EMPID);
EMPXML is an XML type column.
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
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.
Below chart shows the overall enhancements in Teradata 15 release.
| Big Data & Analytics | JSON Integration |
| Scripting and Language Support | |
| Table Operator Enhancements | |
| 3D Geospatial Data Type | |
| Geospatial Performance Enhancements | |
| SQL-H Enhancements | |
| Performance | Light-Weight Redistribution |
| Software Efficiency Improvements | |
| Ecosystem | SQL Interface For ShowBlocks |
| TASM/TIWM - Classification by Datablock Selectivity | |
| Utility Statistics Logging | |
| TASM - Global Weights | |
| Unity Callback Support | |
| TASM - Virtual Partitions Enhancement | |
| TIWM - Operating Periods For Appliance | |
| Quality | Smart Retry During Parsing |
| HSN Health | |
| New PI On Access Rights Table | |
| Unresponsive Node Isolation | |
| Onsite System and Dump Analysis | |
| DBQL - Show Parameters | |
| Industry Compatibility | Sequenced Aggregate Enhancements and Aggregate JI for Temporal |
| 1MB Phase 2 | |
| ANSI Temporal Syntax Support | |
| Teradata Directory Manager |
