Previous Topic

Next Topic

Book Contents

Book Index

Using Transactions

By default, when you run an SQL statement (such as an Update or Delete), the database is immediately changed.

Another option is to run your SQL statement as a Transaction. When this is done:

How to use Transaction Mode

Within both the Run SQL and Row Update windows, you have the option of starting a transaction. This is done with the menu item Transaction > Begin Trans:

Once you have Committed or Rolled back, your transaction is terminated (except when AutoCommit is de-selected - see the next section).


By default, every update you make to the database is applied and committed to the database immediately. This is sometimes referred to as Auto-Commit mode.

You can switch off Auto-Commit mode by de-selecting Options > Technical Parameters > Auto Commit. When auto-commit is switched off:

If you change the Auto Commit option when you are signed onto a database, nothing immediately happens:

If Auto Commit of off, Safe Update Mode will be disabled.

You must Commit or Rollback

Once you have made some changes, a message at the bottom of the screen will warn you of this. It is highly recommended that you Commit or Rollback promptly and do not leave uncommitted changes for any length of time.

AQT Closes without Committing Changes

This can happen if:

In this case, most databases will automatically rollback the outstanding changes. You will have lost any work you have done.

In some circumstances, the AQT process can remain in a suspended state on Windows if is has not terminated cleanly. In this case, it will continue to hold locks and may interfere with other tasks on the database. This may require a DBA to terminate the task on the server.

Other Notes on Transactions

Advanced Query Tool
© 2023 Cardett Associates Ltd. All rights reserved.