---
title: "Explain ACID rule of thumb for transactions."  
description: "Explain ACID rule of thumb for transactions."  
author: "Anonymous User"  
published: 2010-12-31  
updated: 2020-09-21  
canonical: https://www.mindstick.com/interview/307/explain-acid-rule-of-thumb-for-transactions  
category: "db2"  
tags: ["db2"]  
reading_time: 1 minute  

---

# Explain ACID rule of thumb for transactions.

Transaction must be Atomic (it is one unit of work and does not dependent on previous and following transactions), Consistent (data is either committed or roll back, no “in-between” case where something has been updated and something hasn’t), Isolated (no transaction sees the intermediate results of the current transaction), Durable (the values persist if the data had been committed even if the system crashes right after).

## Answers

### Answer by Anonymous User

Transaction must be Atomic (it is one unit of work and does not dependent on previous and following transactions), Consistent (data is either committed or roll back, no “in-between” case where something has been updated and something hasn’t), Isolated (no transaction sees the intermediate results of the current transaction), Durable (the values persist if the data had been committed even if the system crashes right after).


---

Original Source: https://www.mindstick.com/interview/307/explain-acid-rule-of-thumb-for-transactions

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.