The larger your database, the higher the possibility of data repetition and inaccuracies that compromise the results you pull from the database. Normalization in DBMS exists to counteract those problems by helping you to create more uniform databases in which redundancies are less likely to occur.
Mastering normalization is a key skill in DBMS for the simple fact that an error-strewn database is of no use to an organization. For example, a retailer that has to deal with a database that has multiple entries for phone numbers and email addresses is a retailer that can’t see as effectively as one that has a simple route to the customer. Let’s look at normalization in DBMS and how it helps you to create a more organized database.
The Concept of Normalization
Grab a pack of playing cards and throw them onto the floor. Now, pick up the “Jack of Hearts.” It’s a tough task because the cards are strewn all over the place. Some are facing down and there’s no rhyme, reason, or pattern to how the cards lie, meaning you’re going to have to check every card individually to find the one you want.
That little experiment shows you how critical organization is, even with a small set of “data.” It also highlights the importance of normalization in DBMS. Through normalization, you implement organizational controls using a set of principles designed to achieve the following:
- Eliminate redundancy – Lower (or eliminate) occurrences of data repeating across different tables, or inside individual tables, in your DBMS.
- Minimize data anomalies – Better organization makes it easier to spot datasets that don’t fit the “norm,” meaning fewer anomalies.
- Improve data integrity – More accurate data comes from normalization controls. Database users can feel more confident in their results because they know that the controls ensure integrity.
The Process of Normalization
If normalization in DBMS is all about organization, it stands to reason that they would be a set process to follow when normalizing your tables and database:
- Decompose your tables – Break every table down into its various parts, which may lead to you creating several tables out of one. Through decomposition, you separate different datasets, eliminate inconsistencies, and set the stage for creating relationships and dependencies between tables.
- Identify functional dependencies – An attribute in one table may be dependent on another to exist. For example, a “Customer ID” number in a retailer’s “Customer” table is functionally dependent on the “Customer Name” field because the ID can’t exist without the customer. Identifying these types of dependencies ensures you don’t end up with empty records (such as a record with a “Customer ID” and no customer attached to it).
- Apply normalization rules – Once you’re broken down your table and identified the functional dependencies, you apply relevant normalization rules. You’ll use Normal Forms to do this, with the six highlighted below each having its own rules, structures, and use cases.
Normal Forms in DBMS
There isn’t a “single” way to achieve normalization in DBMS because every database (and the tables it contains) is different. Instead, there are six normal forms you may use, with each having its own rules that you need to understand to figure out which to apply.
First Normal Form (1NF)
If a relation can’t contain multiple values, it’s in 1NF. In other words, each attribute in the table can only contain a single (called “atomic”) value.
Example
If a retailer wants to store the details of its customers, it may have attributes in its table like “Customer Name,” “Phone Number,” and “Email Address.” By applying 1NF to this table, you ensure that the attributes that could contain multiple entries (“Phone Number” and “Email Address”) only contain one, making contacting that customer much simpler.
Second Normal Form (2NF)
A table that’s in 2NF is in 1NF, with the additional condition that none of its non-prime attributes depend on a subset of candidate keys within the table.
Example
Let’s say an employer wants to create a table that contains information about an employee, the skills they have, and their age. An employee may have multiple skills, leading to multiple records for the same employee in the table, with each denoting a skill while the ID number and age of the employee repeat for each record.
In this table, you’ve achieved 1NF because each attribute has an atomic value. However, the employee’s age is dependent on the employee ID number. To achieve 2NF, you’d break this table down into two tables. The first will contain the employee’s ID number and age, with that ID number linking to a second table that lists each of the skills associated with the employee.
Third Normal Form (3NF)
In 3NF, the table you have must already be in 2NF form, with the added rule of removing the transitive functional dependency of the non-prime attribute of any super key. Transitive functional dependency occurs if the dependency is the result of a pair of functional dependencies. For example, the relationship between A and C is a transitive dependency if A depends on B, B depends on C, but B doesn’t depend on A.
Example
Let’s say a school creates a “Students” table with the following attributes:
- Student ID
- Name
- Zip Code
- State
- City
- District
In this case, the “State,” “District,” and “City” attributes all depend on the “Zip Code” attribute. That “Zip” attribute depends on the “Student ID” attribute, making “State,” “District,” and “City” all transitively depending on “Student ID.”
To resolve this problem, you’d create a pair of tables – “Student” and “Student Zip.” The “Student” table contains the “Student ID,” “Name,” and “Zip Code” attributes, with that “Zip Code” attribute being the primary key of a “Student Zip” table that contains the rest of the attributes and links to the “Student” table.
Boyce-Codd Normal Form (BCNF)
Often referred to as 3.5NF, BCNF is a stricter version of 3NF. So, this normalization in DBMS rule occurs if your table is in 3NF, and for every functional dependence between two fields (i.e., A -> B), A is the super key of your table.
Example
Sticking with the school example, every student in a school has multiple classes. The school has a table with the following fields:
- Student ID
- Nationality
- Class
- Class Type
- Number of Students in Class
You have several functional dependencies here:
- Student ID -> Nationality
- Class -> Number of Students in Class, Class Type
As a result, both the “Student ID” and “Class” attributes are candidate keys but can’t serve as keys alone. To achieve BCNF normalization, you’d break the above table into three – “Student Nationality,” “Student Class,” and “Class Mapping,” allowing “Student ID” and “Class” to serve as primary keys in their own tables.
Fourth Normal Form (4NF)
In 4NF, the database must meet the requirements of BCNF, in addition to containing no more than a single multivalued dependency. It’s often used in academic circles, as there’s little use for 4NF elsewhere.
Example
Let’s say a college has a table containing the following fields:
- College Course
- Lecturer
- Recommended Book
Each of these attributes is independent of the others, meaning each can change without affecting the others. For example, the college could change the lecturer of a course without altering the recommended reading or the course’s name. As such, the existence of the course depends on both the “Lecturer” and “Recommended Book” attributes, creating a multivalued dependency. If a DBMS has more than one of these types of dependencies, it’s a candidate for 4NF normalization.
Fifth Normal Form (5NF)
If your table is in 4NF, has no join dependencies, and all joining is lossless, it’s in 5NF. Think of this as the final form when it comes to normalization in DBMS, as you’ve broken your table down so much that you’ve made redundancy impossible.
Example
A college may have a table that tells them which lecturers teach certain subjects during which semesters, creating the following attributes:
- Subject
- Lecturer Name
- Semester
Let’s say one of the lecturers teaches both “Physics” and “Math” for “Semester 1,” but doesn’t teach “Math” for Semester 2. That means you need to combine all of the fields in this table to get an accurate dataset, leading to redundancy. Add a third semester to the mix, especially if that semester has no defined courses or lecturers, and you have to join dependencies.
The 5NF solution is to break this table down into three tables:
- Table 1 – Contains the “Semester” and “Subject” attributes to show which subjects are taught in each semester.
- Table 2 – Contains the “Subject” and “Lecturer Name” attributes to show which lecturers teach a subject.
- Table 3 – Contains the “Semester” and “Lecturer Name” attributes so you can see which lecturers teach during which semesters.
Benefits of Normalization in DBMS
With normalization in DBMS being so much work, you need to know the following benefits to show that it’s worth your effort:
- Improved database efficiency
- Better data consistency
- Easier database maintenance
- Simpler query processing
- Better access controls, resulting in superior security
Limitations and Trade-Offs of Normalization
Normalization in DBMS does have some drawbacks, though these are trade-offs that you accept for the above benefits:
- The larger your database gets, the more demands it places on system performance.
- Breaking tables down leads to complexity.
- You have to find a balance between normalization and denormalization to ensure your tables make sense.
Practical Tips for Mastering Normalization Techniques
Getting normalization in DBMS is hard, especially when you start feeling like you’re dividing tables into so many small tables that you’re losing track of the database. These tips help you apply normalization correctly:
- Understand the database requirements – Your database exists for you to extract data from it, so knowing what you’ll need to extract indicates whether you need to normalize tables or not.
- Document all functional dependencies – Every functional dependence that exists in your database makes the table in which it exists a candidate for normalization. Identify each dependency and document it so you know whether you need to break the table down.
- Use software and tools – You’re not alone when poring through your database. There are plenty of tools available that help you to identify functional dependencies. Many make normalization suggestions, with some even being able to carry out those suggestions for you.
- Review and refine – Every database evolves alongside its users, so continued refining is needed to identify new functional dependencies (and opportunities for normalization).
- Collaborate with other professionals – A different set of eyes on a database may reveal dependencies and normalization opportunities that you don’t see.
Make Normalization Your New Norm
Normalization may seem needlessly complex, but it serves the crucial role of making the data you extract from your database more refined, accurate, and free of repetition. Mastering normalization in DBMS puts you in the perfect position to create the complex databases many organizations need in a Big Data world. Experiment with the different “normal forms” described in this article as each application of the techniques (even for simple tables) helps you get to grips with normalization.
Related posts
Source:
- Il Sole 24 Ore, Published on July 29th, 2024 (original article in Italian).
By Filomena Greco
It is called OPIT and it was born from an idea by Riccardo Ocleppo, entrepreneur, director and founder of OPIT and second generation in the company; and Francesco Profumo, former president of Compagnia di Sanpaolo, former Minister of Education and Rector of the Polytechnic University of Turin. “We wanted to create an academic institution focused on Artificial Intelligence and the new formative paths linked to this new technological frontier”.
How did this initiative come about?
“The general idea was to propose to the market a new model of university education that was, on the one hand, very up-to-date on the topic of skills, curricula and professors, with six degree paths (two three-year Bachelor degrees and four Master degrees) in areas such as Computer Science, AI, Cybersecurity, Digital Business; on the other hand, a very practical approach linked to the needs of the industrial world. We want to bridge a gap between formal education, which is often too theoretical, and the world of work and entrepreneurship.”
What characterizes your didactic proposal?
“Ours is a proprietary teaching model, with 45 teachers recruited from all over the world who have a solid academic background but also experience in many companies. We want to offer a study path that has a strong business orientation, with the aim of immediately bringing added value to the companies. Our teaching is entirely in English, and this is a project created to be international, with the teachers coming from 20 different nationalities. Italian students last year were 35% but overall the reality is very varied.”
Can you tell us your numbers?
“We received tens of thousands of applications for the first year but we tried to be selective. We started the first two classes with a hundred students from 38 countries around the world, Italy, Europe, USA, Canada, Middle East and Africa. We aim to reach 300 students this year. We have accredited OPIT in Malta, which is the only European country other than Ireland to be native English speaking – for us, this is a very important trait. We want to offer high quality teaching but with affordable costs, around 4,500 euros per year, with completely online teaching.”
Read the full article below (in Italian):
Source:
- EFMD Global, Published on July 12th, 2024.
By Stephanie Mullins
Many people love to read the stories of successful business school graduates to see what they’ve achieved using the lessons, insights and connections from the programmes they’ve studied. We speak to one alumnus, Riccardo Ocleppo, who studied at top business schools including London Business School (LBS) and INSEAD, about the education institution called OPIT which he created after business school.
Please introduce yourself and your career to date.
I am the founder of OPIT — Open Institute of Technology, a fully accredited Higher Education Institution (HEI) under the European Qualification Framework (EQF) by the MFHEA Authority. OPIT also partners with WES (World Education Services), a trusted non-profit providing verified education credential assessments (ECA) in the US and Canada for foreign degrees and certificates.
Prior to founding OPIT, I established Docsity, a global community boasting 15 million registered university students worldwide and partnerships with over 250 Universities and Business Schools. My academic background includes an MSc in Electronics from Politecnico di Torino and an MSc in Management from London Business School.
Why did you decide to create OPIT Open Institute of Technology?
Higher education has a profound impact on people’s futures. Through quality higher education, people can aspire to a better and more fulfilling future.
The mission behind OPIT is to democratise access to high-quality higher education in the fields that will be in high demand in the coming decades: Computer Science, Artificial Intelligence, Data Science, Cybersecurity, and Digital Innovation.
Since launching my first company in the education field, I’ve engaged with countless students, partnered with hundreds of universities, and collaborated with professors and companies. Through these interactions, I’ve observed a gap between traditional university curricula and the skills demanded by today’s job market, particularly in Computer Science and Technology.
I founded OPIT to bridge this gap by modernising education, making it affordable, and enhancing the digital learning experience. By collaborating with international professors and forging solid relationships with global companies, we are creating a dynamic online community and developing high-quality digital learning content. This approach ensures our students benefit from a flexible, cutting-edge, and stress-free learning environment.
Why do you think an education in tech is relevant in today’s business landscape?
As depicted by the World Economic Forum’s “Future of Jobs 2023” report, the demand for skilled tech professionals remains (and will remain) robust across industries, driven by the critical role of advanced technologies in business success.
Today’s companies require individuals who can innovate and execute complex solutions. A degree in fields like computer science, cybersecurity, data science, digital business or AI equips graduates with essential skills to thrive in this dynamic industry.
According to the International Monetary Fund (IMF), the global tech talent shortage will exceed 85 million workers by 2030. The Korn Ferry Institute warns that this gap could result in hundreds of billions in lost revenue across the US, Europe, and Asia.
To address this challenge, OPIT aims to democratise access to technology education. Our competency-based and applied approach, coupled with a flexible online learning experience, empowers students to progress at their own pace, demonstrating their skills as they advance.
Read the full article below:
Have questions?
Visit our FAQ page or get in touch with us!
Write us at +39 335 576 0263
Get in touch at hello@opit.com
Talk to one of our Study Advisors
We are international
We can speak in: