Any updates to the database that were made between the previous BEGIN TRANSACTION and the END TRANSACTION are committed. If the transaction is the first or only transaction (that is, the transaction isn't nested), the changes are written to disk.

If a transaction is nested, END TRANSACTION causes all cached updates to be folded into the next higher transaction level. Nesting transactions has the potential to overwrite changes made to data at a higher transaction level.

If END TRANSACTION generates an error (for example, there is insufficient disk space to write changes to disk), changes made during the transaction are cancelled and the transaction ends.

Reference

Other Resources