Access modules are dynamically linked software components that provide block-level I/O interfaces to external data storage devices.
Access modules import data from data sources and return it to a Teradata utility. Access modules are dynamically linked to one or more Teradata utilities by the Teradata Data Connector API.
Access modules provide transparent, uniform access to various data sources, isolating you from, for example, device and data store dependencies.
Teradata Database supports the following access modules, which read data, but do not write it.
- Named Pipes Access Module, which enables you to load data into the Teradata Database from a UNIX OS named pipe. A pipe is a type of data buffer that certain operating systems allow applications to use for the storage of data.
- Teradata WebSphere MQ Access Module,which enables you to load data from a message queue using IBM’s WebSphere MQ (formerly known as MQ Series) message queuing middleware.
- Teradata Access Module for JMS, which enables you to load data from a JMS-enabled messaging system using JMS message queuing middleware.
- Teradata OLE DB Access Module, which enables you to transfer data between an OLE DB provider and Teradata Database.
- Custom Access Modules, which you can use with the DataConnector operator for access to specific systems.
Teradata access modules work on many operating systems with the following Teradata Tools and Utilities:
- BTEQ
- Teradata FastExport
- Teradata FastLoad
- Teradata MultiLoad
- Teradata PT
- Teradata TPump