Provider does not depend on the Teradata Call-Level Interface (CLI).
Provider is 100 percent managed code and communicates directly with Teradata Database.
Provider supports XCOPY deployment. You can simply copy the assemblies to the application directory.
New Hierarchical Server Explorer view in Visual Studio 2005. It providers quick access to Data Dictionary objects (Databases, Tables, Views, Stored Procedure and etc.).
Single Click access to SHOW commands (e.g. SHOW TABLE) from Visual Studio 2005 Server Explorer.
Support for expired-password and change-password in Visual Studio 2005.
Support for SELECT statements with over 2000 columns or expressions.
Provider generates Authentication String for LDAP and Kerberos Authentication Mechanisms based on User ID and Password fields. This should greatly simplify application development and interoperability with packaged applications.
Installation can now selectively install the Publisher policy files into the Global Assembly Cache. Previous versions of the provider always installed publisher policy files into the GAC. Publisher Policy files target existing application having a dependency on earlier versions of the provider.
Stored Procedure output parameters are now accessible as very first result set of the TdDataReader if application a) does not bind Input-output or output parameters b) sets the TdCommand.CommandType to CommandType.Text and c) sets the TdCommand.CommandText to the CALL SQL statement. This is a useful feature for ad-hoc query tools that do not support Output or Input-Output parameters.
Provider will cancel pending asynchronous commands when TdConnection is closed.
Teradata Database 12.0 Feature Support:
Stored Procedures can now return Result Sets. Application can invoke TdCommand.ExecuteReader to retrieve a DataReader.
Implicit cast of Date to Timestamp.
Provider now correctly reports expired password events (TdConnection.InfoMessage) and the connection is left open. Application can execute a MODIFY USER statement.
Provider now supports Turkish culture.
Application can now use CommandBehavior.Text to execute CALL statement.