What is the ACID principal?
By: Ramlak in JDBC Tutorials on 2007-04-06
The ACID principal is the foundation which has guided the implementation of transactions in relational databases. This acronym stands for the following:
- Atomicity
- Consistency
- Isolation
- Durability
Atomicity
The term atomicity applies to the ability to group multiple database updates into a single transaction that can be treated as an atomic update. The term atomic is derived from the Greek word for the smallest indivisible element. An atomic transaction is indivisible, since the failure of the one of the updates in the group is considered a failure for the whole group of updates. Either all of the updates will be completed or none be completed, and the transaction will be rolled back, leaving the database in the state it was in before the transaction started.
Consistency
The term consistency applies to the various rules associated with the data in the transactions. These rules may apply to relationships between the tables in the update or to rules concerning the primary key for a table. These rules may be broken during the transaction, but the inconsistent data will not e visible to other users. Once the transaction is complete, the rules must be valid and the database must be in a consistent state.
Isolation
A given transaction should appear as though it is running alone in the database. The work of other users must be coordinated with other transactions to maintain this isolated view. The work of other transactions is invisible to the user in a transaction.
Durability
The work of a committed transaction is guaranteed to persist and remain in the database even in the event of various system failures. A transaction is not considered durable until it commits. A system failure entails a database recovery, which includes a rollback procedure for all uncommitted transactions, ultimately leaving the database in a consistent state.
Add Comment
This policy contains information about your privacy. By posting, you are declaring that you understand this policy:
- Your name, rating, website address, town, country, state and comment will be publicly displayed if entered.
- Aside from the data entered into these form fields, other stored data about your comment will include:
- Your IP address (not displayed)
- The time/date of your submission (displayed)
- Your email address will not be shared. It is collected for only two reasons:
- Administrative purposes, should a need to contact you arise.
- To inform you of new comments, should you subscribe to receive notifications.
- A cookie may be set on your computer. This is used to remember your inputs. It will expire by itself.
This policy is subject to change at any time and without notice.
These terms and conditions contain rules about posting comments. By submitting a comment, you are declaring that you agree with these rules:
- Although the administrator will attempt to moderate comments, it is impossible for every comment to have been moderated at any given time.
- You acknowledge that all comments express the views and opinions of the original author and not those of the administrator.
- You agree not to post any material which is knowingly false, obscene, hateful, threatening, harassing or invasive of a person's privacy.
- The administrator has the right to edit, move or remove any comment for any reason and without notice.
Failure to comply with these rules may result in being banned from submitting further comments.
These terms and conditions are subject to change at any time and without notice.
- Data Science
- Android
- React Native
- AJAX
- ASP.net
- C
- C++
- C#
- Cocoa
- Cloud Computing
- HTML5
- Java
- Javascript
- JSF
- JSP
- J2ME
- Java Beans
- EJB
- JDBC
- Linux
- Mac OS X
- iPhone
- MySQL
- Office 365
- Perl
- PHP
- Python
- Ruby
- VB.net
- Hibernate
- Struts
- SAP
- Trends
- Tech Reviews
- WebServices
- XML
- Certification
- Interview
categories
Related Tutorials
Data Access Technologies in Java
JDBC and Tomcat context settings
TEXT datatype SPLIT in MSSQL - to solve the 8000 limit set by varchar
What is Referential Integrity in databases?
Handling CSV in Stored Procedures
java.lang.NoClassDefFoundError and java.lang.NoSuchMethodError
Calling a Stored Procedure from JDBC in Java
setSavepoint and releaseSavepoint Example in Java
Result Sets, Cursors and Transactions in SQL
Stored Procedures example in SQL
Using the DriverManager Class vs Using a DataSource Object for a connection
Comments