Data redundancy is a condition created within a database or data storage technology in which the same piece of data is held in two separate places. Or in the case of a flat file database, there are records with partly duplicated data. For example Jones, 48, Male, Teacher
Jones, 48, 3 Advent Drive
Jones, employee number 22345
As you can see in the records above, the name is repeated three times and the age is duplicated twice. Whenever data is repeated, this basically constitutes data redundancy. This can occur by accident, but is also done deliberately for backup and recovery purposes.
What is Data inconsistency
Data inconsistency is when different and conflicting versions of the same data appear in different places in a database. This causes unreliable information, because it is difficult to determine which version of the information is correct. It’s difficult to make correct and timely decisions if those decisions are made based on conflicting information. Consistency talks about ensuring that any transaction will bring the database from one valid state to another. Any data written to the database must be valid according to all defined rules. Data inconsistency is likely to occur when there is data redundancy. That’s why one major goal of good database design is to eliminate data redundancy. For example, in a banking transaction that debits a savings account and credits a checking account, a failure must not cause the database to credit only one account, which would lead to inconsistent data. Atomicity of update
The Term Paper on Databases And Information Management
1. Introduction Database systems are the information heart of modern enterprises, where they are used for processing business transactions and for understanding and managing the enterprise. Business intelligence is the analysis of data to produce insights useful for managing the enterprise and increasingly, in routine business operations such as intelligent supply chain management. The knowledge ...
Atomicity is a feature of databases systems dictating where a transaction must be all-or-nothing. 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. The transaction must either fully happen, or not happen at all. It must not complete partially.
