| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CLR Integration and Transactions |
For CLR integration and transactions, System.Transactions and ADO.NET work together to extend and simplify the use of local and distributed transactions in managed applications. |
rwestMSFT |
randolphwest |
12/27/2024 |
sql |
clr |
reference |
|
[!INCLUDE SQL Server]
The System.Transactions namespace provides a transaction framework that is fully integrated with ADO.NET and [!INCLUDE ssNoVersion] common language runtime (CLR) integration. System.Transactions and ADO.NET work together to extend and simplify the use of local and distributed transactions in managed applications.
Note
A CLR user-defined procedure (UDP) can't establish a connection to the same server it's running on (a loopback connection) and enlist in the same transaction. If this is attempted, the connection attempt will be blocked and control will not be passed back to the UDP. This will result in a timeout error (Msg 1206) on the UDP.
For more information about transactions and the .NET Framework, see Transaction Processing.
| Article | Description |
|---|---|
| Transaction promotion | Describes the ability to promote transactions, and how to use this feature. |
| Access the current transaction | Describes how to access a transaction currently running in-process on [!INCLUDE ssNoVersion]. |
| Use System.Transactions | Describes how to use the System.Transactions application programming interface (API) in your managed application. |
| Transaction lifetimes | Describes the difference in lifetime between transactions started in [!INCLUDE tsql] stored procedures and transactions started in CLR applications. |