Represents an Explicit SQL Transaction. It should be
explicitly committed or rolled back.
Object Model
Syntax
'Declaration Public NotInheritable Class TdTransaction Inherits System.Data.Common.DbTransaction Implements System.Data.IDbTransaction, System.IDisposable
'Usage Dim instance As TdTransaction
public sealed class TdTransaction : System.Data.Common.DbTransaction, System.Data.IDbTransaction, System.IDisposable
public ref class TdTransaction sealed : public System.Data.Common.DbTransaction, System.Data.IDbTransaction, System.IDisposable
Remarks
By default TdConnection object operates in Auto-Commit mode. Therefore the transaction spans the execution of one or more TdCommand object. The application can open a transaction via TdConnection.BeginTransaction and explicitly control when the transaction is committed or rolled back.
the Advanced SQL Engine will rollback a transaction when a SQL statement results in a specific set of errors. In this case, the .NET Data Provider for Teradata will open a new explicit transaction and the TdTransaction object can be used to commit or abort the remaining activities associated with the TdConnection object.
The TdConnection object reverts back to Auto-Commit mode after an explicit call by the application to TdTransaction.Rollback or TdTransaction.Commit method.
Unlike the ODBC Driver and OLE DB Provider for Teradata, the .NET Data Provider for Teradata does not automatically commit a transaction after a DDL statement execution. Therefore, the DDL statement has to be the last SQL statement within a transaction. Furthermore the DDL statement cannot be part of a multi-statement request.
Inheritance Hierarchy
System.Object
System.MarshalByRefObject
System.Data.Common.DbTransaction
Teradata.Client.Provider.TdTransaction
Requirements
Target Platforms: Windows 8.1, Windows 10, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019
See Also