- 1 Vapor IO Brings OpenDCRE to General Availability
- 2 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 3 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 4 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 5 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
|SWatch Reader Favorite! A poor database design can cripple an application, producing problems with data redundancy, accuracy, consistency and concurrency. Normalization reduces, if not eliminates, these problems.|
First, normal forms requires there be no multi-valued attributes, and no repeating groups. A multi-valued attribute would contain more than one value for that field in each row.
Consider the following StudentCourses table:
In this table, the Course field is a multi-valued attribute. There is not a single value for each field.
Now, consider this StudentCourses table:
The Course1, Course2, Course3 fields represent repeating groups.
proper way to store this data follows. First Normal form is
In the first two designs, selecting students that are enrolled in a certain course is difficult. Say I want to do the following:
Tell me all of the students enrolled in course 3100. In the first design, you'll have to pull all of the course data and parse it somehow. And in the second design, you'll have to check 3 different fields for course 3100. In the final design, a simple Select StudentID from StudentCourses where Course=3100.
Original date of publication, 02/21/2001