The TPT DataConnector Operator is the mechanism by which TPT obtains data from or sends data to external native operating system flat (sequential) files or attached access modules.

This article will address the data formats usable with the TPT DataConnector Operator. For each format, we will first deal with the concept of a record, which roughly maps to a DBS table row. Secondly, we will address how these data are resolved to row columns using the TPT data schema. When these two requirements are validated, we will have converted the external data record to a Teradata DBS row. If not, we have a fatal data error*.

In this post, we will cover some more advanced logging topics in TRM, including PE logging, SQL output, user clicks, authentication attempts, and startup logging.

While transactional processing through the use of “message queues” is a common approach in ADW today, the file-oriented approach is also begining to find its way into ADW due to its simplicity in nature and ease-of-control. Today, many companies monitor and store thousands--or hundreds of thousands--of transactions per day across their branches and stores. Transactional data is usually collected and stored as files in directories, before being merged into the enterprise-wide data warehouse. In fact, there have been Teradata sites which extract transactional data from message queues, pre-process them, and store them into different directories based on transaction types, in an “active” manner. By “active”, we mean the files are created as transactions are collected.

The Teradata Parallel Transporter (TPT) External Command Interface is a command based interface which allows users to issue commands to TPT jobs. The term “external commands” implies two important implementations. First, it implies that users can issue commands to TPT jobs from outside the TPT address space. Secondly, it implies that commands are processed by TPT while it is in the middle of performing ETL operations. In addition, TPT internal components such as operators (which run under different processes) can also communicate with each other within a job through the same interface by using commands. As a result, ETL and system “events” are not only shared between the TPT and users, but also shared amongst TPT components within a job at runtime.

In the first article in this series on Teradata Error Handling, we introduced the larger architecture and load utility environment. in this article the focus will be on the Fastload Utility and some of the techniques applicable to handling errors, exceptions and failures that can occur within a High Availability system.

This article describes the basics of TRM's V6 logging in the application server. This includes log file configuration, versioning, location and content.

The availability of Teradata's geospatial extension package in 2007 brought these location capabilities to Teradata 12, 6.2 and 6.1.  This package is still available as a free download from Teradata and when installed, adds geospatial functionality as a User Defined Type (UDT) along with a library of User Defined Functions (UDFs).  (See my article on downloading and installing this package).  One of the major highlights of Teradata 13 is the inclusion of thes