16.10 - Known Issues for .NET Data Provider for Teradata - Teradata Tools and Utilities

Teradata Tools and Utilities for Microsoft Windows Installation Guide

prodname
Teradata Tools and Utilities
vrm_release
16.10
created_date
April 2018
category
Installation
featnum
B035-2407-048K
The following installation issues are recognized for .NET Data Provider for Teradata. Suggestions are provided for working around the installation issues.
  • Installing a newer version of .NET Data Provider for Teradata without first uninstalling the older version, a side-by-side installation, is not recommended. If you uninstall any version of .NET Data Provider for Teradata after a side-by-side installation, the registry key HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\.NETFramework\AssemblyFolders\Teradata Data Provider is removed. In addition, Microsoft Visual Studio no longer lists .NET Data Provider for Teradata in the AddReference dialog box.
    To resolve this uninstallation issue after a side-by-side installation, do the following:
    1. Go to Control Panel > Programs and Features.
    2. In the list of installed programs, do one of the following for .NET Data Provider for Teradata depending on the Windows version:
      • Click Change, select Repair, and click Next
      • Right-click the item and click Repair
  • Use the FullTrust permission set of Microsoft .NET Framework to run .NET Data Provider for Teradata. Security in the .NET Framework provides more information about the FullTrust permission set.
  • For Microsoft Visual Studio 2008, note the following integration issues:
    • TableAdapter Query Configuration Wizard does not generate correct parameters for the INSERT Query type. Visual Studio 2008 Dataset bug provides more information about this issue.
    • TdDataAdapter Configuration Wizard does not generate unique names for commands. The wizard always generates the names SelectCommand, InsertCommand, UpdateCommand, and DeleteCommand for the corresponding instances of the TdCommand class.

      To configure more than one TdDataAdapter, change the name of auto-generated commands to prevent conflict with the command names generated for the first instance of TdDataAdapter. For example, if the first instance of TdDataAdapter uses the name SelectCommand, rename the second instance to SelectCommand1.