Transaction Processing

With Adaptive Server ADO.NET Data Provider, you can use the AseTransaction object to group statements together.

Each transaction ends with a COMMIT or ROLLBACK, which either makes your changes to the database permanent or cancels all the operations in the transaction, respectively. When the transaction is complete, you must create a new AseTransaction object to make further changes. This behavior is different from ODBC and Embedded SQL, where a transaction persists after you execute a COMMIT or ROLLBACK until the transaction is closed.

If you do not create a transaction, Adaptive Server ADO.NET Data Provider operates in autocommit mode by default. There is an implicit Commit after each insert, update, or delete, and when an operation is completed, the change is made to the database. In this case, the changes cannot be rolled back.

• Isolation Level Setup for Transactions
  You can choose to specify an isolation level when you begin the transaction. The isolation level applies to all commands executed within the transaction.
• Support for Transact-SQL Queries with COMPUTE clause
  Adaptive Server ADO.NET Data Provider supports Transact-SQL queries that include a COMPUTE clause.