What is a 'ACID' Database

Posted by: Mark K. Lame on 06/9/06 04:34 PM

Occasionally, you here the acronym 'ACID' compliant when describing a database. What does the acronym 'ACID' stand for?


The database we chose for our product 'WrapDB' is 'ACID' compliant. How WrapDB manages data is critical to it's function, read on for more info...



The list above represent how data is managed at a specific period in time. Let's take the first - Atomicity: All elements of a given transaction take place or none do. What is this saying? Nothing, absolutely nothing will interfere with the transaction. So, a database server lost power while you deposited money in the bank. The transaction won't be partial but rolled back.

Consistency - Each transaction transforms the database from one valid state to another valid state. Suppose triggers are placed on the transaction. If the trigger cannot determine if it should fire, yes or no, the transaction rolls back.

Isolation - The results of a transaction are invisible to other transactions until the transaction is complete. Example - You withdrawal $200 from the bank, the transaction has not committed yet. Same time, your bank is generating your monthly statement. The $200 withdrawal will not appear on the statement because you hadn't committed it yet.

Durability - Once committed (completed), the results of a transaction are permanent and survive future system and media failures. It's written in stone, simple as that!

WrapDB manages critical medical information which must be 100% correct. We felt maintaining 100% data integrity a necessity considering the service WrapDB provides.