a marker that the user puts inside a transaction to indicate a point to which it can be rolled back
a named point in a transaction that you can rollback to without rolling back the entire transaction
a user-defined marker within a transaction that allows portions of a transaction to be rolled back
A SAVEPOINT is a kind of bookmark that we may revert to with ROLLBACK. Entering “SAVEPOINT backup1” during a session will preserve the state of the database before we created the SAVEPOINT
A point in the workspace to which operations can be rolled back. It is analogous to a firewall, in that by creating a savepoint you can prevent any damage to the "other side" of the wall (that is, operations performed in the workspace before the savepoint was created). See also explicit savepoint, implicit savepoint, and removable savepoint.
Set a point to which you can later roll back. Also see Commit and Rollback.
A savepoint is a way of implementing subtransactions (also known as nested transactions) within a relational database management system by indicating a point within a transaction that can be "rolled back to" without affecting any work done in the transaction before the savepoint was created. Multiple savepoints can exist within a single transaction. Savepoints are useful for implementing complex error recovery in database applications — if an error occurs in the midst of a multiple-statement transaction, the application may be able to recover from the error (by rolling back to a savepoint) without needing to abort the entire transaction.
