What describes a save point in a transaction?

What describes a save point in a transaction?

• A. The final commit of a transaction.
• B. A designated point within a transaction to which you can roll back.
• C. A backup copy stored on disk outside the transaction.
• D. A log entry created at transaction start.

Answer: (B)

A save point is a designated point inside a transaction that lets you roll back to it without aborting the entire transaction. It acts like a bookmark so you can undo only the operations that happened after that point, keeping earlier changes intact within the same transaction. This is useful for error handling or complex sequences where you want to recover from a problem without starting over from scratch. It’s not the final commit, which makes all changes permanent, and it’s not a separate backup outside the transaction, nor a log entry created at the start. In practice, you create a save point (SAVEPOINT), roll back to it (ROLLBACK TO SAVEPOINT) if needed, and later can commit the whole transaction or release the savepoint if supported. For example, you might perform several inserts, establish a save point after the first, continue with the rest, and roll back to that save point if a later step fails, preserving the earlier work within the same transaction.

A save point is a designated point inside a transaction that lets you roll back to it without aborting the entire transaction. It acts like a bookmark so you can undo only the operations that happened after that point, keeping earlier changes intact within the same transaction. This is useful for error handling or complex sequences where you want to recover from a problem without starting over from scratch. It’s not the final commit, which makes all changes permanent, and it’s not a separate backup outside the transaction, nor a log entry created at the start. In practice, you create a save point (SAVEPOINT), roll back to it (ROLLBACK TO SAVEPOINT) if needed, and later can commit the whole transaction or release the savepoint if supported. For example, you might perform several inserts, establish a save point after the first, continue with the rest, and roll back to that save point if a later step fails, preserving the earlier work within the same transaction.