0 - 22 of 22 tags for v_connectivity

The RJDBC package enables an R application to use the Teradata JDBC Driver to access the Teradata Database.

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.

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.

With the introduction of Query Grid in Teradata 15, many people have been asking "what about me? I am on not going to be on TD 15 for some time.".

In this series of articles I provide a tool I call DbLink which provides a similar capability for versions of Teradata prior to 15.0. The DbLink tool consists of a Table UDF and supporting components that may be used to access data from a remote RDBMS via JDBC.

The Teradata Connector for Hadoop (TDCH) provides scalable, high performance bi-directional data movement between the Teradata database system and Hadoop system.

JDBC support has been added to teradataR version 1.0.1 which provides the ability of using the Teradata JDBC Driver through teradataR to connect to the Teradata database.  teradataR allows R users to easily connect to a Teradata database and use statistical functions directly against the Teradata system without having to extract memory into data.  For mor

This reference guide provides information about the Teradata JDBC Driver, which is a Teradata Tools and Utilities product. A set of Frequently Asked Questions is also available.

Teradata has completed a major compiler conversion effort that should be completely transparent to customers, yet they are the main beneficiaries.  This article:

  • Provides some historical background and context,
  • Discusses the reasons we switched compilers,
  • Identifies certain behavioral changes that were unavoidable,
  • And, finally, answers a few technical questions related to the overall process.

The venerable IBM mainframe was the original client platform developed for the Teradata RDBMS via channel-attached connections way back in the 1980s. Although we now support a wide range of client platforms using network-attached connections, a significant segment of our customer base continues to use mainframe clients.

The following reference documentation is available:

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

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 - 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 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.

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.

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. 

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:

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.

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.

This article introduces CLIv2 debug facility and describes Client and Teradata DBS server wire protocol. There are two parts of this article. The first part is to cover how to setup CLIv2 debug facility. It includes the setting of many environment variables that activate different function of CLIv2 debug facility. The second part is to describe the contents generated by CLIv2 debug facility. It covers messages and parcels sent and received between Client and DBS servers.

Teradata offers many ways to connect and query our database with our Tools and Utilities(TTU) package - BTEQ, BTEQWin, SQLA and the TD Eclipse plug-in.

HTML boasts a wide range of features to present data to end users. Add in the various frameworks that “sit on top” of HTML and the web represents a rich and powerful environment through which information may be delivered to end users.

While the web is a powerful environment, there are times when a windows based application might be better suited to the task at hand. This article presents a Java class library that makes this a lot easier.