Welcome! Teradata Developer Exchange is a community-oriented website that connects Teradata Associates with Customers and others interested in the related technologies. Think of it as a technical collaborative community for sharing ideas, asking questions, learning, and solving problems related to Teradata solutions and beyond. Sounds great doesn't it? So sign up and join the community now!

Expand All Subscribe to Teradata Developer Exchange - All content The Latest
New Teradata Unity Data Mover 15.00 Available

Announcing Teradata Unity Data Mover 15.00

We are pleased to announce the General Customer Availability (GCA) of Unity Data Mover 15.00. With release 15.00, Unity Data Mover is now certified with Teradata Database 15.00, and supports important database features such as JSON and foreign server definitions. Data Mover can now move foreign server definitions, as well as utilize QueryGrid/foreign server connections to move data from Hadoop to Teradata (if installed). Hadoop support has also been extended to support TDH 2.1 and 1.3.2.

Data Collection for a Solid Performance Management Foundation

This presentation will review the benefits of collecting performance data on the Teradata platform.

Introduction to Teradata Active System Management (TASM)

TASM gives customers the ability to manage Teradata resource usage and performance on platforms executing diverse types of work.

A Quick Tour of the XML Type

A Quick Tour of XML Type

Teradata Query Grid and Machine Learning in Hadoop

This article describes how to use Teradata query grid to execute a Mahout machine learning algorithm on a Hadoop cluster based on data sourced from the Teradata Integrated Data Warehouse. Specifically the Mahout K-means cluster analysis algorithm is demonstrated.  K-means is a computationally expensive algorithm that under certain conditions is advantageous to execute on the Hadoop cluster. Query Grid is an enabling technology for the Teradata Unified Data Architecture (UDA).

A Closer Look at How to Set up a Parsing-Only Workload

When you think about priorities, you probably focus your attention on AMP work.  Whether you are using Teradata Active System Management (TASM) or Teradata Integrated Workload Management (TIWM), AMP work performed by requests are typically spread across different workloads, with their priorities based on the importance of the work to the business and how long you expect the work to run.

Parsing engine work on behalf of a query runs within a workload as well.  Work performed on the parsing engine is typically very quick and requires very few resources.  So why not run some, or all, of your parsing activity in a very high priority workload where it may be able to complete sooner when your system is busy,  just as you do with your short, critical AMP work?  This posting will explain how parsing priority is determined, and will illustrate the steps involved in increasing parsing priority.

Working with Identity Columns and Unity Director and Loader

One of Unity Director and Loader’s core benefits is the ability to keep multiple Teradata systems synchronized with online, transactional-consistent, changes. Unlike post-transactional replication, Unity Director’s SQL-multicast sends requests in parallel to all connected systems at the same time. It also performs consistent checking on the responses of every write statement to ensure changes both systems succeed and produce the same results.

Access External Data - Part 2 Add support for other data sources

The DbLink facility allows Teradata users to access data in external systems. However, as distributed, it only supports accessing data from external Oracle and Teradata systems.

In this article we will look at what is required to add support for other data sources. As it turns out, not much, just some basic Java programming abilities.

XML Query

Querying XML

Access External Data - Part 1 The Table UDF

Many databases provide the ability for accessing external data via a mechanism via a SELECT query. Examples include Linked Tables in MS-Access and External Tables in Oracle. A similar capability will become available in Teradata 15, it will be known as Query Grid. However users of Teradata prior to 15 are out of luck.

Teradata has provided the foundation for accessing external data via a SELECT query ever since Table UDF's were added in or around Teradata 12. There is even reference in the UDF programmers manuals to just such a facility (but no actual code to show how to do it).

In this article, you can download a working facility I've called DbLink that you can setup and use to access data from external data sources without having to write your own UDF.

Pages