This PPT SLide contain information of Transaction State and Achid Property in DBMS. this PPT created by www.meribaate.in This ppt is worthy for Database student who need to study about Transaction state and Acid Property. this Slide present good information about ACID property in DBMS.

1. ACID
PROPERTY
Created by
www.meribaate.in

2. • The ACID properties are a set of characteristics
that are essential for ensuring the reliability
and consistency of transactions in a database
system
• Reliability refers to the ability of a system or
component to perform its functions under
specific conditions for a specified period of
time

3. • Consistency, in the context of databases and
data management, refers to the requirement
that a database must transition from one valid
state to another. This means that any changes
made by a transaction must adhere to the
rules and constraints defined by the database
schema.

4. Atomicity
• This property ensures that a transaction is
treated as a single, indivisible unit of work.
Either all of the operations within the
transaction are successfully completed, or
none of them are. There is no partial
completion of a transaction. If any part of a
transaction fails, the entire transaction is
rolled back to its original state.

5. Consistency
• After a transaction is completed, the database
must transition from one consistent state to
another. This means that any integrity
constraints, such as foreign key relationships
or unique constraints, must be maintained.
The database should not be left in a state
where data is improperly linked or violates any
defined rules.

6. Sleep

7. Isolation
• This property ensures that multiple
transactions can occur concurrently without
interfering with each other.
• Each transaction should be isolated from the
others in such a way that it appears as if it is
the only transaction executing on the system.
This prevents interference between
concurrent transactions

8. Durability
• Once a transaction is successfully completed,
the changes it made to the database should
persist even in the event of system failures
(such as power outages, crashes, or errors).
• This means that the changes are recorded in
non-volatile storage (like disk) and are not lost
even if the system restarts.

9. State of Transaction

10. • In Database management, a “State of
Transaction" refers to the current condition or
phase of a transaction's execution within a
database system.
• Transactions go through various stages.

11. Active
• This is the initial state of a transaction. In this
state, the transaction is performing its
operations, such as reading or writing data
from the database.

12. Partially Committed
• At some point during the transaction's
execution, it may reach a stage where all of its
operations have been successfully completed.
• The system then enters the partially
committed state, indicating that the
transaction is ready to be finalized, but it
hasn't been confirmed yet.

13. Committed
• Once a transaction is successfully completed,
it enters the committed state. In this state, all
the changes made by the transaction are
considered permanent and are guaranteed to
be preserved, even in the event of system
failures.

14. Failed
• If a transaction encounters an error or
encounters a condition that prevents it from
completing successfully, it enters the failed or
aborted state.

15. Terminated
• This is the final state of a transaction that has
failed or been explicitly rolled back by the
system.
• In this state, any changes made by the
transaction are reversed, restoring the
database to its state before the transaction
started.

16. Thank You
Please Visit – www.meribaate.in