Within a stored procedure, is a nested transaction considered autonomous?

• A. False
• B. Depends
• C. True
• D. Not supported

Answer: (C)

The key idea is that a nested transaction inside a stored procedure has its own transaction boundary, separate from the outer transaction. Because of that, the inner block can be committed or rolled back independently of the outer scope. The outer transaction remains active until it’s explicitly committed or rolled back later, so you can structure logic where a portion of work is isolated and managed on its own terms. This autonomy lets you handle partial success and targeted error recovery inside a single procedure without forcing the entire operation to commit or revert at the inner level.