We have seen conditions for 4NF in the last article. Now let’s move on to 5NF. Let’s say, different brands make different flavors of ice cream. Brand A : Vanilla and Strawberry flavor Brand B : Chocolate, Vanilla and Strawberry flavor Brand C : Strawberry and Chocolate flavor Ron likes…

We have seen conditions for 3NF in the last article. Now let’s move on to 4NF. Model #1 Color: Yellow, Green Shape: Circle, Square Model #2 Color: Blue Shape: Triangle, Square Here, we have 2 models, and we know their color and shapes as well. …

We examined conditions for 2 NF in the last post. Let’s move on to 3 NF, also known as Boyce-Code form. Here identifying transitive dependency is vital. Although the table is already in 2 NF but still there is a possibility of anomaly. A person of age 5 can either…

We talked about 1NF in the previous post. We need to understand Functional Dependencies first. There are many Rons across many departments. That’s why Name and Dept together can form a Primary Key here. Key attributes are Name & Dept. Age and Dept Head are non-key attributes. Functional Dependency : …

We saw the anomalies that could sweep in a design, making to a bad data base design. Let’s see what we can do to avoid them or at least reduce the chances. There are Normal forms ranging from 1 NF to 5 NF ensuring higher safety levels. First rule: Every…

If you want the same concepts explained in Marathi, its here. In order to design a good database, we need to learn some rules in order to avoid anomalies. Typically, following anomalies are often found. Insertion anomaly Update anomaly Deletion anomaly Here, rows are repeated, causing Redundancy. Update anomaly Let’s…

You can enroll here.