It states that database modifications must follow an \u201call or nothing\u201d rule. Each transaction is said to be \u201catomic.\u201d If one part of the transaction fails, the entire transaction fails. It is critical that the database management system maintain the atomic nature of transactions in spite of any DBMS, operating system or hardware failure.
It states that only valid data will be written to the database. If, for some reason, a
transaction is executed that violates the database\u2019s consistency rules, the entire
transaction will be rolled back and the database will be restored to a state consistent with
those rules. On the other hand, if a transaction successfully executes, it will take the
database from one state that is consistent with the rules to another state that is also
consistent with the rules.
It requires that multiple transactions occurring at the same time not impact each other\u2019s
execution or One transaction does not interfere with another. The 'executor' of a
transaction has the feeling that he has the entire database for himeself.
A commited(Saved) transaction will not be lost. Durability is ensured through the use of
database backups and transaction logs that facilitate the restoration of committed
transactions in spite of any subsequent software or hardware failures.
Database normalization can essentially be defined as the practice of optimizing table
structures. Normalization helps us to elimate redundant data and to store the data we have
in a manner that makes sense. Atomicity also must be maintained in tables via
normalization. Normalization helps us to create atomic tables by removing redundant
data within rows of a table, thus creating atomic tables.
Let\u2019s take a look at some denormalized data. I\u2019m going to use the simplest example that
comes to mind, and that is a auto repair shop that specializes in domestic automobiles
(domestic to the US, that is). Our table lists automobile manufactuers and the makes of
automobiles they manufactuer that the shop services.
As you can see, 1NF is already enforcing the atomic nature of a table. So first we need to
remove duplicate columns from the table, at the same time creating column by row
positions that have unique values, which means we also have to seperate Saturn, Buick
into individual values.
For each level of normal form, the next level must adhere to the rules of the previous
level, in addition to adding its own rules. This means in order to create a data structure
that meets the requirements of 2NF, we must first meet the requirements of 1NF. We
have already discussed the rules for 1NF, so let\u2019s look at the rules required to meet 2NF.
This action might not be possible to undo. Are you sure you want to continue?