Microsoft Connector for Teradata (SSIS)
Applies to: SQL Server SSIS Integration Runtime in Azure Data Factory
Microsoft Connector for Teradata enables exporting and loading data into Teradata databases in an SSIS package.
This new connector supports databases with 1MB-enabled tables.
Microsoft Connector supports the following Microsoft SQL Server products for Teradata:
- Microsoft SQL Server 2019
- Microsoft SQL Server 2022
- SQL Server Integration Services Projects for Visual Studio 2019
- SQL Server Integration Services Projects for Visual Studio 2022
Microsoft Connector for Teradata uses ODBC Driver for Teradata, and Teradata Parallel Transporter shipped with Teradata Tools and Utilities (TTU). Supported TTU versions are 16.20 and 17.10.
Install TTU from Teradata site. Make sure that ODBC Driver for Teradata and Teradata Parallel Transporter features is selected during the installation.
To install the connector for the Teradata database, download and run the installer from the latest version of Microsoft connector for Teradata. Then follow the directions in the installation wizard.
To design packages with SQL Server Integration Services Projects, you will need to install the connector for both the target and the latest SQL Server version.
After you install the connector, you must restart the SQL Server Integration Service to be sure that the Teradata source and destination work correctly.
Design and execute SSIS packages
Microsoft Connector for Teradata provides a similar user experience to Attunity Teradata Connector. Users can design new packages based on previous experience, using SSDT for VS 2017 or VS 2019, with targeting SQL Server 2019.
Teradata source and destination are under Common category.
Teradata connection manager is displayed as "TERADATA."
Existing SSIS packages designed with Attunity Teradata Connector will be automatically upgraded to use Microsoft Connector for Teradata. The icons will be changed as well.
To execute the SSIS package targeting SQL Server 2017 and below, you'll need to install Microsoft Connector for Teradata by Attunity with corresponding version from the below link:
- SQL Server 2017: Microsoft Connector Version 5.0 for Teradata by Attunity
- SQL Server 2016: Microsoft Connector Version 4.0 for Teradata by Attunity
- SQL Server 2014: Microsoft Connector Version 3.0 for Teradata by Attunity
- SQL Server 2012: Microsoft Connector Version 2.0 for Teradata by Attunity
To design the SSIS package in SSDT targeting SQL Server 2017 and below, you'll need to have Microsoft Connector for Teradata and install Microsoft Connector for Teradata by Attunity with the corresponding version.
Limitations and known issues
Teradata Source/Destination Editor, Default database property doesn't take effect. As a workaround, type the database name in dropdown box to filter table or view.
Teradata Source/Destination Editor, Mapping step doesn't work when type
\<database>.<table/view>. As work-around, type
\<database>.<table/view>, then select the drop-down button.
Teradata Source Editor, view can't be displayed when Data access mode is "Table Name – TPT Export." As work-around, use Advanced Editor of Teradata Source.
Teradata Destination, attribute "PackMaximum" can't be set to "True." Otherwise, error will occur.
Teradata Source always reads columns in the order as they're defined in the table. ODBC, on the other hand, requires columns be read in a specific order in certain circumstances Getting Long Data and SQLGetData. When the two orders don't match, read fails with error message "Invalid descriptor index, descriptor record doesn't exist, or descriptor record wasn't properly initialized."
Installing a new version over an old installation won't remove the old version entry from the installed program list. While this doesn't impact functioning of the new version, user can manually uninstall the old version in the control panel "Programs, and Features" to get rid of the old version entry.
You can uninstall wizard to remove Microsoft connector for Teradata.
- Teradata Destination will crash under certain circumstances.
- Teradata Destination will report success despite errors occurred under certain circumstances.
- Teradata Destination will report a larger number of rows written than reality under certain circumstances.
- When error occurred, Teradata Destination will retain and direct user to TPT error tables for investigation.
- Memory leak in Teradata Destination.
- Teradata Destination fails with error message "an error occurred when converting string from source codepage" when consuming empty strings.
- Under certain circumstances, Data Flow Task reports success despite errors occurred in Teradata Destination.
- Teradata Destination fails when writing
VARCHARvalues with a very large length.
- Improved performance of Teradata Destination.
- Teradata Connection Manager logs error detail for connection failure.
- When processing tabular data with 24 or more columns, an error will occur with message
[Teradata][ODBC] (10670) Invalid descriptor index, descriptor record does not exist, or descriptor record was not properly initialized.
- A newly created Teradata Connection Manager will default to latest version Teradata ODBC driver installed even when it is not supported.
- In a newly created Teradata Connection Manager, some required connection string properties like
DRIVERaren't populated by default.
- Add support for TTU 17.10.
- Teradata Source may load incorrect data under certain circumstances.
- Default error table in Teradata Destination is incorrectly named and may not be created in the database of the destination table.
- Options specified in the connection string property of Teradata Connection Manager may not be picked up and therefore don't take effect.
- When reading empty string data, Teradata Source would fail with the error message "An error occurred when converting string to target codepage."
- Configure Teradata connection manager
- Configure Teradata source
- Configure Teradata destination
- If you have questions, visit Tech Community