TdConnectionStringBuilder.SessionCharacterSet property supports Windows Compatible Session Character Sets (e.g. LATIN1252_3A0 and KANJI932_1S0) introduced in Teradata Database 12.0. Please refer to Teradata Database International Character Set Support manual for additional information about Windows compatible session character sets.
The Data Provider now supports Integer Date. The Data Provider can receive Integer Date from the Teradata Database 12.0 or higher. However it only sends ANSI Date to the Teradata Database. Applications and/or end users can execute "SET SESSION DATEFORM=INTEGERDATE" DDL statement to change the session to Integer Date mode. We recommend ANSI Date (default); Integer Date should only be used for backward compatibility with legacy applications or scripts.
The Data Provider now supports Statement Independence when connected to Teradata 13.10 or later release. The Data Provider only supports this feature from the TdDataAdapter. Support of Statement Independence by the Data Provider will improve the performance of batch updates under scenarios where the only INSERT statements are submitted to Teradata and one or more of them fail. For more information on how Statement Independence affects batch updates when using the TdDataAdapter refer to Batch Update.
The Data Provider integrates with the Microsoft Visual Studio 2010 and it also operates in the .NET Framework 4.0 (CLR 4.0). The Entity Provider for Teradata supports ADO.NET Entity Framework 3.5 SP1 features. The Entity Provider does not support ADO.NET Entity Framework 4.0 features.
In a few specific cases the Data Provider threw an exception when an application and/or user sets the "Data Source" to an IP-Address literal. The exception was generated by the DNS reverse lookup. The Data Provider has been enhanced to always connect to an IP-Address literal. However, SPNEGO authentication will fail when the Data Provider cannot retrieve the Host Name associated with the IP-Address from DNS.
The .NET Framework Stopwatch class may return a negative Elapsed time on some machines with specific BIOS. The Data Provider threw ArgumentException from TdConnection.Open method because a negative Elapsed Time is not valid. The Data Provider has been enhanced to workaround this issue.
Releases of Teradata 12.0 and earlier do not support sub-queries in the column-list of a SELECT statement. The Entity Provider for Teradata can generate a sub-query in the column-list depending upon the LINQ for Entities or Entity SQL statement that it is processing. The provider does detect a sub-query is to be created under most scenarios. However, some scenarios were missed. A scenario that was not detected by the provider is now checked. When the Entity Provider is connected to a 12.0 or earlier release of Teradata a NotSupportedException is now thrown that includes a more informative error message than what would be returned from Teradata.
The Teradata Database returned error "3945: Invalid data length for VarChar, VarByte or VarGraphic" when TdDataAdapter.UpdateBatchSize is not set to 1 and TdParameter.Size property is not set to the maximum length of the corresponding column. The Data Provider now infers the TdParameter.Size property when application fails to set it to a value greater than zero.
The .NET Data Provider threw an exception when Federal Information Processing Standard (FIPS) monitoring was turned on. The Data Provider used a noncompliant SHA1 managed implementation. The Data Provider now uses a FIPS compliant SHA1 implementation.
The Data Provider returned error "3116: Response Buffer size is insufficient to hold one record" when Input Parameters to the TdCommand object included one or more Large Objects (BLOB or CLOB) and the result set row size exceeded the specified Response Buffer Size. The Data Provider now automatically adjusts the Response Buffer Size and internally handles error 3116.
The support for the Views and ViewColumns store schemas was not included in the 13.10 release. These store schemas are now supported by the Entity Provider. To enable support, entries must be added to the application configuration file. The entries describe a mapping between each schema and a table. The mapped table must also be loaded with the corresponding metadata. A new utility called SchemaLoader.exe has been added to the Teradata Provider installation that is used to load the metadata into the mapped tables. Refer to Mapping Views and ViewColumns to Tables for more information.
In an isolated scenario the Data Provider threw an ArgumentOutOfRangeException (Parameter name: responseMsgSize) when the SELECT statement accessed a View with 100s of columns. The Data Provider now handles this scenario.