The phrase "all or nothing" succinctly describes the first ACID property of atomicity. When an update occurs to a database, either all or none of the update becomes available to anyone beyond the user or application performing the update. This update to the database is called a transaction and it either commits or aborts. This means that only a fragment of the update cannot be placed into the database, should a problem occur with either the hardware or the software involved.
Features to consider for atomicity:
a transaction is a unit of operation - either all the transaction's actions are completed or none are
atomicity is maintained in the presence of deadlocks
atomicity is maintained in the presence of database software failures
atomicity is maintained in the presence of application software failures
atomicity is maintained in the presence of CPU failures
atomicity is maintained in the presence of disk failures
Data Analytics Startup Lands MySpace As Early Adopter InformationWeek, NY - May 14, 2008 ... against large data stores: 1) scale up by adding processors to a DBMS; 2) deploy a DBMS across a massively parallel cluster; 3) write custom code. ...
Of All Things, IBM Takes a Lead in the Mashup Fray Intelligent Enterprise, CA - 21 hours ago IBM's DB2 v9 pureXML, which merges the power of a respected SQL database management system with a truly integrated XML database engine, is a tour de force ...
Data archiving: For the users, by the users SearchCIO.com - May 15, 2008 Olofson agrees the archiving approach means companies can put the data in a place where the database management system doesn't need to manage it anymore, ...
ParAccel and Talend Form Alliance Business Wire (press release), CA - May 13, 2008 ?Business intelligence and analytics bring special requirements to the database management system, and the ability to access cross-platform data is a ...
Transaction Processing: Concepts and Techniques (The Morgan Kaufmann Series in Data Management Systems) by Jim Gray, Andreas Reuter Average Customer Review: based on 9 reviews. Customer Review: For nearly a decade this book has been the definitive reference on transaction processing. Although the more recent, May 2001 book titled "Transactional Information Systems: Theory, Algorithms, and the Practice of Concurrency Control" by Gerhard Weikum and Gottfried Vossen will probably supplant this book as the standard reference, t...
Roger Jennings' Database Workshop: Microsoft Transaction Server 2.0 by Steven D. Gray, Rick A. Lievano, Roger Jennings Average Customer Review: based on 17 reviews. Customer Review: I purchased the book in order to get up-to-speed with MTS. Although it left some unanswered questions, the book lived up to its promise to get me up-and-running with MTS in a flash. Using the sample code as a basis, I built and deployed my first MTS app in a little less than a month. A follow-up book providing deeper insight into th...
Databases and Transaction Processing: An Application-Oriented Approach by Philip M. Lewis, Arthur Bernstein, Michael Kifer Average Customer Review: based on 4 reviews. Customer Review: Database and Transaction Processing by Philip M. Lewis, et al. is written as a multi-purpose textbook and practical reference guide for software engineers. One can use this book both as an undergraduate introductory course in database theory and design, as an advanced graduate-level course in databases, or as a graduate level course ...
based on 9 reviews.
based on 17 reviews.
based on 4 reviews.
based on 1 review.
