Transactional Database
Transactional Database
database is a DBMS where write operations on the database are able to be rolled back if they are not completed properly.
If a transactional database system loses electrical power half-way through a transaction, the partially completed transaction will be rolled back and
the database will be restored to the state it was in before the transaction started.
Transactional Database has the functionality or an important role required to maintain consistency and integrity
in the database.
Any database transaction (read from database or write into the database) must be Atomic, Consistent and have
Integrity, Durability popularly called in short as the ACID property of the database design.
1) A database management system should be able to recover from any kind of failure during a transaction
automatically like power failures or other interruptions.
Imagine that a front-end application is sending a customer order to a database system. The front-end application
sends the request to product to the customer and subtract the product from inventory. The front-end application
is about to send the request to create an invoice for the customer and suddenly the front-end application
crashes.
Transactional database provides functionality called ‘Roll back’ to overcome such losses. When a transaction did
not complete the roll back statement rolls the database to the state before beginning of the transaction which
failed. This helps to avoid any kind of loss and lets you start the transaction again afresh.