{"id":3440,"date":"2021-07-06T15:55:19","date_gmt":"2021-07-06T10:25:19","guid":{"rendered":"https:\/\/www.goseeko.com\/blog\/?p=3440"},"modified":"2026-01-16T10:55:04","modified_gmt":"2026-01-16T05:25:04","slug":"what-is-acid-property","status":"publish","type":"post","link":"https:\/\/www.goseeko.com\/blog\/what-is-acid-property\/","title":{"rendered":"What is ACID Property?"},"content":{"rendered":"\n
A transaction in a database system must maintain Atomicity, Consistency, Isolation, and Durability \u2212 commonly known as ACID property \u2212 in order to ensure accuracy, completeness, and data integrity.<\/p>\n\n\n\n
\n
Atomicity<\/li>\n\n\n\n
Consistency<\/li>\n\n\n\n
Isolation<\/li>\n\n\n\n
Durability<\/li>\n<\/ul>\n\n\n\n
Atomicity<\/strong>: –<\/h2>\n\n\n\n
\n
A transaction is an atomic unit of processing.<\/li>\n\n\n\n
It is either performed entirely or not performed at all.<\/li>\n\n\n\n
Means either all operations are reflected in the database or none are.<\/li>\n\n\n\n
It is the responsibility of the transaction recovery subsystem to ensure atomicity.<\/li>\n\n\n\n
moreover, If a transaction fails to complete for some reason, the recovery technique must undo any effects of the transaction on the database.<\/li>\n<\/ul>\n\n\n\n
Consistency<\/strong>: –<\/h2>\n\n\n\n
\n
A transaction is consistency preserving if its complete execution takes the database from one consistent state to another.<\/li>\n\n\n\n
It is the responsibility of the programmer who writes database programs.<\/li>\n\n\n\n
Database programs should be written in such a way that, if the database is in a consistent state before execution of transaction. After That it will be in a consistent state after execution of transaction.<\/li>\n\n\n\n
For instance, Transaction is :- Transfer $50 from account A to account B.<\/li>\n\n\n\n
If account A having amount $100 & account B having amount $ 200 initially then after execution of transaction, A must have $ 50 & B must have $ 250.<\/li>\n<\/ul>\n\n\n\n
Isolation<\/strong>: –<\/h2>\n\n\n\n
\n
If multiple transactions execute concurrently. They should produce the result as if they are working serially.<\/li>\n\n\n\n
Further, It is enforce a concurrency control subsystem.<\/li>\n\n\n\n
To avoid the problem of concurrent execution, transactions should be executed in isolation.<\/li>\n<\/ul>\n\n\n\n
Durability<\/strong>: –<\/h2>\n\n\n\n
\n
The changes applied to the database, by a committed transaction must persist in a database.<\/li>\n\n\n\n
The changes may not be lost because of any failure.<\/li>\n\n\n\n
It is the responsibility of the recovery subsystem of the DBMS.<\/li>\n<\/ul>\n\n\n\n