Canceling an Interactive SQL Command

Use the Interrupt button on the Interactive SQL toolbar to cancel a command.

A Stop operation stops current processing and prompts for the next command. If a command file was being processed, you are prompted for an action to take (Stop Command File, Continue, or Exit Interactive SQL). You can control these actions with the Interactive SQL ON_ERROR option.When an interruption is detected, one of three different errors is reported, depending on when the interruption is detected. If the interruption is detected:

When Interactive SQL is processing the request (as opposed to the database server), this message appears, and Interactive SQL stops processing immediately and the current database transaction is not updated:
```
ISQL command terminated by user
```
By the database server while processing a data manipulation command (select, insert, delete, or update), this message appears, and the effects of the current command are left unfinished but the rest of the transaction is left intact:
```
Statement interrupted by user.
```
While the database server is processing a data definition command (create object, drop object, alter object, and so on.), this message appears:
```
Terminated by user -- transaction rolled back
```
Since data definition commands all perform a commit automatically before the command starts, rollback simply cancels the current command.
This message also occurs when the database server is running in bulk operations mode executing a command that modifies the database (insert, update, and delete). In this case, rollback cancels not only the current command, but everything that has been done since the last commit. In some cases, it may take a considerable amount of time for the database server to perform the automatic rollback.