Data Integrity

Data Integrity

Scenario for the application being built in which a series of steps must be performed as a transaction rather than individually. The scenario involves transferring $50,000 from account X to Y while crediting each account with a 2% interest payment. As both transactions will be made at the same time, there is no telling which transaction will be executed before the other. Nonetheless, the outcome will be that the transactions follow one another serially. Accordingly, the steps for the transactions include beginning the transaction, making it active, and issue a READ or WRITE operation (Thakur, n.d.). After this phase, the transaction becomes partially committed. The recovery protocols are activated to ensure that the money transfer and crediting activities remain intact. The transaction can either be successful or a failure. If, for instance, the client cancels the money transfer the active state, the entire process goes back to the failed state. The aborted phase entails returning before the transaction took place, and the data is rolled back to the database. The last stage is the committed stage, which signifies the success of the process. The stages ensure each transaction has expected outcomes.

What could happen to the data if only partial statements were executed. The transaction is considered failed when partial statements are executed (Mullins, 2017). If any data check fails in the active phase, the transaction fails altogether. The terminated state further ensues because transactions exiting the system cannot be restarted.

Application of Acid Properties for accuracy, integrity, and completeness. The ACID properties ensure that the transaction has integrity, completeness, and accuracy. Atomicity, for one, means that the transaction must exude ‘all or nothing’ qualities (Mullins, 2017). This ensures that all the processes of the transaction are achieved, leading to accuracy and completeness. Comparatively, consistency ensures that the data is accurate before and after the transaction is complete. As such, the transaction is guaranteed accuracy, integrity, and completeness. Durability is also relevant as the database will hold the information even when the system fails or restarts. The transaction details will retain their accuracy, integrity, and completeness of the transaction. Finally, isolation treats all transactions a single transaction even when they happen simultaneously. The integrity, completeness, and accuracy of the data for a transaction remain intact even if they are many. The ACID properties foster transaction success.

References

Mullins, C. (2017). The role of ACID in the integrity of your database data. Database Trends and Applications. Retrieved from http://www.dbta.com/Columns/DBA-Corner/The-Role-of-ACID-in-the-Integrity-of-Your-Database-Data-121440.aspx

Thakur, D. (n.d.). What is transaction in DBMS? Explain process, states, and properties of transaction. Ecomputer Notes. Retrieved from http://ecomputernotes.com/database-system/rdbms/transaction