The ADO.NET Entity Framework is now supported. The Entity Provider for Teradata supports .NET Framework 3.5 SP1.
New Node-Down detection algorithm to quickly and automatically bypass nodes that are down or otherwise unresponsive. NodeDownTimeout Connection-String attribute is obsolete because Data Provider no longer tracks Down-Nodes.
TdCommandBuilder.QuoteIdentifier and TdCommandBuilder.UnquoteIdentifier are now supported. These methods properly escape or unescape embedded quotes within the identifier.
TdConnection.State supports a broken connection state, returned when a data source encounters an error. The TdConnection may only be closed and reopened when in the broken state.
ValidTime: A column can be specified as VALIDTIME only if its data type is PERIOD(DATE) or PERIOD(TIMESTAMP[(n)] [WITH TIME ZONE]) data types.
TransactionTime: A column can be specified as TRANSACTIONTIME only if its data type is PERIOD(TIMESTAMP(6) WITH TIME ZONE).
The following schema collections have been modified to support temporal columns.
Tables Schema Collection TABLE_TYPE_EX has been expanded to return information that indicates temporal columns exist as ValidTime, TransactionTime or Bi-temporal (both ValidTime and TransactionTime).
Columns Schema Collection has a new column named TEMPORAL_TYPE that returns temporal type information.
Indexes Schema Collection has 3 new columns named VALIDTIME_CONSTRAINT, TRANSACTIONTIME_CONSTRAINT, and UNIQUE_OR_PK. The constraints may be current, sequential or non-sequential for temporal table indexes. The UNIQUE_OR_PK column indicates a temporal table index is unique or a primary key.
PrimaryKeys Schema Collection has a new column named UNIQUE_OR_PK. The UNIQUE_OR_PK column indicates a temporal table index is unique or a primary key.
Fixed possible data corruption when a command is forcefully closed (not Canceled) and connection is returned back to the pool. There are two ways to Cancel / Abort a long running query namely a) TdCommand.Cancel method is invoked or b) TdConnection.Close is invoked while a long-running query is executing. "TdConnection.Close" way of aborting a long-running query might (highly unlikely) result in data-corruption or errors because a single buffer might be shared across two DataReaders when Connection is retrieved from the pool (DR 145182).
Data Provider can now execute and return result-set(s) for MACRO with embedded ECHO statement. The Data Provider no longer returns error 100016 "Invalid Teradata response message sequence". ECHO statements are skipped similar to Data Provider version 12.0 and earlier. The Use Enhanced Schema Table Connection String attribute will no longer change the Data Provider behavior in relation to the ECHO statements (DR 133480).
Teragss, the security component now correctly supports Authorizations for SPNEGO mechanisms. For example the authorization string 'diperm01@@secret user=perm01' is now supported correctly (DRs 125863 and 133635). Please see the Teradata Database Security Administration manual topic "Teradata Database Authentication and Authorization" for more information.
Teragss now supports mixed case domain names against Linux authentication servers. For example this domain was not recognized properly - platinum.CliKrbdom.teradata.com during a lookup from the server because of the mixed case in the domain name (DR138225).