Connectivity covers the mechanisms for connecting to the Teradata Database, including driver connectivity via JDBC or ODBC.

Expand All Subscribe to Teradata Developer Exchange - Connectivity content The Latest
OLE DB Access Module amj file having multiple jobs

OLE DB Access Module amj files or Access Module Job files contain the following information:

  • Data source details (Database Name, Driver used to connect to database) for the both source and destination.
  • Table name for the data source supplying data
  • List of columns for the data source supplying data

All the information is stored in XML format and is stored under a JOB element.

Data Warehousing in a Virtual World: Cloud Computing and Beyond

Virtualization is an increasingly important foundation for cost-effective deployment of data warehouse capability. This session will trace the evolution of virtualization technologies in the context of data warehousing and will extrapolate toward future developments in this area.

Creating an OData service using .NET Data Provider for Teradata

The Open Data Protocol (OData) is a protocol to share or exchange data over the web.  The protocol was developed by Microsoft in 2007 as part of the ADO .NET Data Services technology (a.k.a. Project Astoria) for creating and consuming data services using the Web. This protocol became widely used that Microsoft gave the protocol its own identification, named it OData and considered ADO.NET Data Services as the .NET implementation of OData.

ODBC Learning Examples

ODBC Learning Examples - Tier 2 is a suite of applications designed to provide an informative guide to developing ODBC applications as well as providing simple building blocks for ODBC applications.  The samples are split into eleven distinct modules. Within each module there is a range of applications usually with a unifying lesson in mind. This document contains instructions for the use and the descriptions behind each module and the sample applications contained within that module.

JMS Access Module 13.0 Efix available

JMS Access Module is an interface between JMS Queues and the Teradata standalone load utilities such as FastLoad, MultiLoad, and Tpump. These utilities use the JAVA messaging services (javax.jms) application programming interface (API) to connect to queues / topics and feed data to load utilities through the Java Native Interface (JNI) because all standalone load utilities are C / C++ applications.

Laddered Concurrent Connect (LCC): Client Performance Improvements

Have you ever experienced a Node Panic or Down Node?  Do you have Hot Standby Nodes (HSN's) in your configuration?  

If you answered 'YES' to any of these questions, read-on about how Teradata has introduced a new feature that may improve performance in these types of situations.

Visual Studio Server Explorer Integrated with .NET Data Provider for Teradata

The .NET Data Provider for Teradata is integrated with Microsoft's Visual Studio 2005 and 2008.  This article addresses the Visual Studio Server Explorer integration with a Teradata data connection and the various database objects that are supported. 

Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems 13.10

This book provides reference information for Teradata Call-Level Interface Version 2 (CLIv2) for channel-attached systems, which is the native interface between application programs on the client system and the Teradata Relational Database Management System (RDBMS). The product provides access to Teradata from mainframe client environments.

CLIv2 for channel-attached systems uses:

Teradata Director Program Reference 13.10

This book provides information about the Teradata Director Program (TDP), which resides in the mainframe client and manages communication between CLIv2 client application programs and the Teradata server. The functions of the TDP include:

Speed up your JDBC/ODBC applications

The Teradata JDBC Driver and ODBC Driver allow developers to quickly build applications that interact with the Teradata Database. However, many developers are surprised when their fully functioning application suddenly hits a performance roadblock when it is deployed to their production environment. And in many of these cases, the blame is sometimes unfairly placed onto the JDBC and ODBC drivers. This article will highlight the programming techniques available to maximize the performance when interacting with the database and help developers choose the right implementation.