- DBMS Tutorial
- What is Database Management System (DBMS)?
- Components of DBMS
- Applications of DBMS
- Three Schema DBMS Architecture
- Difference between DBMS and RDBMS?
- Difference between File Oriented System and DBMS
- Types of Data Models
- DBMS Schema and Instances
- Data Independence and Data Abstraction
- Database Users and Administrator
- DBMS Languages and Interfaces
DBMS ER Model
DBMS Relational Data Model
States of Transaction in DBMS
The States of transaction in DBMS cycle through several states in its life cycle. These states are called transaction states. The transaction put up in one of the pursuing states in the database.
Active state is the initial state in each transaction life cycle. The transaction is said to be in an active state though it begins executing and implement, read, and write operations.
Partially Committed State
This state is also known as the execution phase. Several transactions come into this state when the last operation of the transaction takes performed, and merely the record is not stored in the database.
Some transactions accomplished the implementation adequately, and because all the modifications made in the local memory through the partially committed state are forever saved in the database.
A transaction enters this state when it is not able to proceed in a normal manner, either due to its internal error or due to some system failure.
This transaction state appears after the transaction has been rolled back, and the database has been reconstructed to its state before the beginning of the transaction.
A transaction is said to be terminated when it has either committed successfully or has aborted after a failure.
Transaction were beginning in the active state. And when it completed its last declaration, it comes to the partially committed state. The transaction has done its implementation. Still, there is just feasibility that it could be revoked, because the real output can even, temporarily occupy in main memory, and because the hardware failure can break its prosperous accomplishment.
When the database framework writes out successfully the output data to disk, then the transaction enters the committed state.
The transaction can also come to the failed state from the active state or the partially committed state after the framework decides that the transaction can no longer continue with its normal implementation considering of hardware failure or logical error. Transaction should be rolled back, and the record has been re-saved to its state before the beginning of the transaction. Formerly, it is called the aborted state. The system has two options are as follows:
- Restart the Transaction:
It can re-start the transaction because mainly some the transaction was aborted as an outcome of any hardware failure or software bug. The re-started transaction is advised to be the new transaction.
- Kill the Transaction:
It can kill the transaction because of a few internal logical bug which can be rectified particularly by rewriting the software program, or because the input was terrible.
Enroll Yourself in Live Training: DBMS Training