Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Transaction processing is a mandatory requirement of all applications that must guarantee consistency of their persistent data. With the Microsoft JDBC Driver for SQL Server, transaction processing can either be performed locally or distributed. Transactions are atomic, consistent, isolated, and durable (ACID) modules of execution.
The articles in this section describe how the JDBC driver supports transactions including isolation levels, transaction savepoints, and result set holdability.
In this section
| Article | Description |
|---|---|
| Understanding transactions | Provides an overview of how transactions are used with the JDBC driver. |
| Understanding XA transactions | Provides an overview of how XA transactions are used with the JDBC driver. |
| Understanding isolation levels | Describes the various isolation levels that are supported by the JDBC driver. |
| Using savepoints | Describes how to use the JDBC driver with transaction savepoints. |
| Using holdability | Describes how to use the JDBC driver with result set holdability. |