Database Transaction Operation

A Database Transaction Operation is an information system transaction in a transaction database system that can be treated independently of other database transactions.

• Context:
  • It can (typically) be a set of Information Processing Operations.
  • It can range from being an Atomic Transaction to being a Non-Atomic Transaction.
  • It can range from being an Consistent Transaction to being a Non-Consistent Transaction.
  • It can range from being an Isolated Transaction to being a Non-Isolated Transaction.
  • It can range from being an Durable Transaction to being a Non-Durable Transaction.
  • It can range from being a Online Database Transaction to being an Offline Database Transaction.
• Context:
  • It can be an ACID Transaction.
  • It can be a BASE Transaction.
  • …
• Counter-Example(s):
  • a Business Transaction.
• See: Business Transaction Record, TPC Benchmark.

---

---

References

2013

• http://en.wikipedia.org/wiki/Database_transaction
  • A transaction comprises a unit of work performed within a database management system (or similar system) against a database, and treated in a coherent and reliable way independent of other transactions. Transactions in a database environment have two main purposes:
    1. To provide reliable units of work that allow correct recovery from failures and keep a database consistent even in cases of system failure, when execution stops (completely or partially) and many operations upon a database remain uncompleted, with unclear status.
    2. To provide isolation between programs accessing a database concurrently. If this isolation is not provided, the program's outcome are possibly erroneous.
  • A database transaction, by definition, must be atomic, consistent, isolated and durable. Database practitioners often refer to these properties of database transactions using the acronym ACID.

    Transactions provide an "all-or-nothing" proposition, stating that each work-unit performed in a database must either complete in its entirety or have no effect whatsoever. Further, the system must isolate each transaction from other transactions, results must conform to existing constraints in the database, and transactions that complete successfully must get written to durable storage.

---