Making Changes Permanent

Use the COMMIT statement to make all changes permanent.

The default action in DBISQL is to do a COMMIT on exit. This can be controlled with the dbisql option COMMIT_ON_EXIT.

dbisql has another option named AUTO_COMMIT. If this option is on, DBISQL does a COMMIT operation after every command. The default for this option is OFF. Usually you will want it OFF, giving you the opportunity to ROLLBACK the changes if, for example, a delete operation doesn’t produce the intended results.

For more information on dbisql options, see Utility Guide.

Note: Use COMMIT with care. When trying the examples in this tutorial, be careful not to COMMIT any changes until you are sure that you want to change the database permanently.

While Sybase IQ excels at bulk changes in a single transaction, overhead for each transaction is higher than a traditional OLTP database. (Also true at the statement level.) This means that COMMIT statements may take longer to complete than in an OLTP system, but in a data warehousing environment, there tend to be fewer commits than in OLTP systems.

Increased overhead from frequent COMMIT operations affects your system performance.