TdConnectionStringBuilder has been changed to support selecting Redrive and Recoverable Network Protocol (RNP) support. Two new properties (described below) have been added to enable and manage RNP and Redrive - TdConnectionStringBuilder.Recovery and TdConnectionStringBuilder.ProfileName.

• Selecting Redrive and RNP Participation Using TdConnectionStringBuilder.Recovery

  TdConnectionStringBuilder.Recovery enables RNP and Redrive, if the feature is available from the database. There are 4 settings supported in Recovery:

Recovery Setting	Description
Off	Disables RNP and Redrive.
Default	Enables Redrive participation as determined from the Teradata Active System Management (TASM) Redrive setting.
Rnp	Enables the session to reconnect in the event of a network error or database failure. Commands may be re-executed and results retrieved after reconnection from a network failure only.
Redrive	Enables Redrive. The connection will participate in redriving commands after reconnection. Redrive enhances the RNP option, as the Teradata Database spool files are preserved after a database restart when REDRIVE is selected. Commands will be re-executed or restarted automatically from the Data Provider.

• Selecting a Profile Name from the Application Configuration File Using TdConnectionStringBuilder.ProfileName

  The application configuration file for the .NET Data Provider for Teradata has been enhanced to support adding custom profile names.These profile names are added to support changing the new reconnection properties as well as any of the listed properties in the Configuration File Provider Section. The profile is enabled by setting TdConnectionStringBuilder.ProfileName to the profile name in the application configuration file. A default profile ("default") name may also be added to support default properties to either supplement all profile names or to supply all the properties by using the "default" profile name from the TdConnectionStringBuilder.ProfileName. The Configuration File Provider Section provides a detailed description of the the application configuration file profile names, the default profile name and applying these properties to the ConnectionString.

See Also

Configuration File Provider Section