The savepoint statement establishes a point within an MQT to which the transaction can be aborted. This enables your application to partially undo the effects of a transaction instead of aborting the entire transaction. All database changes performed by the transaction after the savepoint are rolled back. All changes preceding the savepoint remain.

If the same savepoint name is used in multiple savepoint statements within an MQT, the most recently executed savepoint is always in effect. There is no limit to the number of savepoint declarations allowed within a transaction.