Tools covers the tools and utilities you use to work with Teradata and its supporting ecosystem. You'll find information on everything from the Teradata Eclipse plug-in to load/extract tools.

Expand All Subscribe to Teradata Developer Exchange - Tools content The Latest
Understanding Named Pipe Access Module data transfer

The Teradata Named Pipe Access Module (NPAM) provides an inter-process communication link between a writer process (such as FastExport) and a reader process (such as FastLoad).

What's a BOM and Why do I Care?

The Unicode™ standard defines five encodings (the first three encodings are currently supported by Teradata):

Structuring Requests in BTEQ for Retryable (and Other) Errors

The Teradata RDBMS can return a variety of errors. Some of these errors are retryable (that is, the request can be resubmitted); the simplest example of this is a 2631 (Transaction aborted due to %VSTR) caused by a deadlock condition. Other errors are not retryable; data-related errors (constraint violations, etc.) are an example.

For certain retryable error codes, BTEQ will, by default, retry the failing request. The user can disable such retries via the SET RETRY command. For example, if a 2631 occurs, and retries have not been disabled, BTEQ will resubmit the request.

Teradata Enterprise Data Warehouse Business Intelligence Perspective

Teradata Enterprise Data Warehouse Business Intelligence Perspective - Module 1 - BOBJ/Teradata Implementation Best Practices

Using TPT Easy Loader to move data within the database environment

If you’re waiting for an easy way to load data from one or more Teradata table(s) into a Teradata table without writing a Teradata PT script, wait no further.  Teradata PT Easy Loader can do it easily.  In the 14.0 release, the tool can load data from a Teradata table or from SELECT statement(s).

The Named Pipe Access Module introduces the “pipe_wait” parameter

About the NPAM

The Teradata Named Pipe Access Module provides an inter-process communication link between a writer process (such as FastExport) and a reader process (such as FastLoad).

Where it started:

Teradata Data Mover Portlet: Job level security

Teradata Data Mover (version 13.10) introduced job level security management which allows users to specify access rights at job level. Through the Teradata Data Mover Portlet, a Viewpoint user with access to Data Mover Portlet can grant/revoke access rights of individual Data Mover job to other Viewpoint users with access to Data Mover portlet. 

Teradata Data Mover Portlet: Create your first job

Teradata Data Mover (version 13.10) introduced a graphical user interface component (Portlets) that allows users a more intuitive way to copy database objects from one Teradata database system to another. The Portlet component compliments and enhances the existing ‘command line’ component. It is deployed on Teradata Viewpoint Web portal & gives users an opportunity to manage Data Mover jobs from the convenience of a Web browser. 

Dynamic Partial Table Copies with Teradata Data Mover

In the last Teradata Data Mover (TDM) article (Executing Partial Table Copies with Teradata Data Mover), we discussed creating a TDM job to copy a subset of rows in a table between Teradata systems. This example showed how customers can avoid copying an entire table to the target system when they only want to copy recent changes made to that table. The problem with the example in that article, though, is that the where clause has a hard-coded value in it. Customers will typically want to avoid having hard-coded values in their production TDM partial copy jobs because the subset of rows they want to copy will change every time they want to execute the job. It's possible for customers to just create a new TDM job every time they want to change the where clause, but that could lead to many unnecessary jobs being created in the TDM repository that copy data from the same table. It's much more efficient to create one job that will copy a dynamic subset of rows every time it is executed. Executing the same TDM job repeatedly instead of creating a new job every time rows need to be copied from the same table will eliminate the overhead associated with creating new TDM jobs.

Executing Partial Table Copies with Teradata Data Mover

In the last Teradata Data Mover (TDM) article (Introduction to Teradata Data Mover: Create your first job), we discussed creating and executing a TDM job to copy a full table between Teradata systems. This use case is very common in the field when customers want to initially populate the target Teradata system with the same table that exists on the source Teradata system. Customers will not want to copy the entire table to the target system every time changes are made to the source system though. Tables on production systems can get quite large and it doesn't make sense to copy the entire table when only a subset of rows have been changed since the last copy took place. This is why TDM supports executing partial table copies as well as full table copies.

Pages