Scribd
Upload
72 views3 pages

Transaction Properties

A transaction is a logical unit of work that reads or updates data in a database. It must follow the ACID properties of atomicity, consistency, isolation, and durability to maintain the integrity of the database. The core database modules that handle transactions are the transaction manager, scheduler/lock manager, and recovery manager.

Uploaded by

gopi9966957145
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
72 views3 pages

Transaction Properties

A transaction is a logical unit of work that reads or updates data in a database. It must follow the ACID properties of atomicity, consistency, isolation, and durability to maintain the integrity of the database. The core database modules that handle transactions are the transaction manager, scheduler/lock manager, and recovery manager.

Uploaded by

gopi9966957145
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Transaction support:

Transaction:
An action, or series of actions, carried out by a single user or application
program that reads or updates the contents of the database.
A transaction is treated as a logical unit of work on the database.
It may be an entire program, a part of a program, or a single statement
(for example, the SQL statement INSERT or UPDATE).
Example:
A simple transaction against this database is to update the salary of a
particular member of staff given the staff number, x.

State transition:
A transaction can have one of two outcomes. If it completes successfully,
the transaction is said to have committed.
On the other hand, if the transaction does not execute successfully, the
transaction is aborted.
If a transaction is aborted, the database must be restored to previous state.
Properties of Transactions:

There are properties that all transactions should possess.


The four basic, or so called ACID, properties that define a transaction are

• Atomicity: The “all or nothing” property. A transaction is an indivisible


unit that is either performed in its entirety or is not performed at all. It is
the responsibility of the recovery subsystem of the DBMS to ensure
atomicity.

• Consistency: A transaction must transform the database from one


consistent state to another consistent state. It is the responsibility of both
the DBMS and the application developers to ensure consistency.

The DBMS can ensure consistency by enforcing all the constraints that
have been specified on the database schema, such as integrity constraints.

• Isolation: Transactions execute independently of one another. In other


words, the partial effects of incomplete transactions should not be visible
to other transactions. It is the responsibility of the concurrency control
subsystem to ensure isolation.

• Durability: The effects of a successfully completed (committed)


transaction are permanently recorded in the database and must not be
lost because of a subsequent failure. It is the responsibility of the recovery
subsystem to ensure durability.
Database Architecture:

Database Architecture consists of four high-level database modules that


handle transactions, concurrency control, and recovery.
The transaction manager coordinates transactions on behalf of application
programs. It communicates with the scheduler, the module responsible for
implementing a particular strategy for concurrency control.
The scheduler is sometimes referred to as the lock manager if the
concurrency control protocol is locking-based.
The objective of the scheduler is to maximize concurrency without
allowing concurrently executing transactions.
If a failure occurs during the transaction, then the database could be
inconsistent. It is the task of the recovery manager to ensure that the
database is restored to the state.
Finally, the buffer manager is responsible for the efficient transfer of data
between disk storage and main memory.

You might also like