Home > Articles > Data

Database Normalization for the Real World

Why is normalization important? Many databases today are still denormalized for many reasons. This article, by April Wells, addresses some of the reasons and normalizes a claim table through the different normal forms for an insurance company. The changes in the table and the addition of more tables in the process make the database more efficient, less prone to error, and more maintainable.
Like this article? We recommend Terminology - Title Page

Database normalization is the practice (sometimes practice and practice and practice) of optimizing table structures and organizing the data into tables so the data will always be as unambiguous as intended. Normalization allows you to adapt to changing business rules, changing requirements, and changing data without having to restructure the entire system.

By altering the way you store your data—just a little bit—and changing the programs that are accessing that information, you can eliminate many opportunities for incorrect or corrupt data and ease the effort required for updating information.

One of the banes of a company's existence is the statement, "We have always done it that way." We have always stored the information like that; we have always allowed people to just put anything into that <insert field name>; we have always programmed that way. That isn't always a bad thing, especially when a company is young and learning. Yet, sometimes "the way things have always been done" may need to be revisited and revised when there is a new system and a better way of doing things. Normalizing data is one of the times and ways that are an advantage to the company to adopt.

Although data can be stored in a relational database similar to the way it would be stored in a flat file for use by a COBOL program (like a file layout that any COBOL programmer is familiar with), that process isn't necessarily the best way of doing it, especially if you are simply carrying the ideas of the past over into the present because you don't understand the difference or are afraid of change.


Dictionary.com defines normalization this way: "To make normal, especially to cause to conform to a standard or norm," or "The imposition of a standard." Oh that's helpful. Webopedia says normalization is: "In relational database design, the process of organizing data to minimize redundancy. Normalization usually involves dividing a database into two or more tables and defining relationships between the tables. The objective is to isolate data so that additions, deletions, and modifications of a field can be made in just one table and then propagated through the rest of the database via the defined relationships" I like this definition better....


Before you look at normalization in connection with a real-world example of insurance information, you need to become comfortable with some of the terminology that is used in the discussion. When dealing with databases, and particularly on the subject of normalization, a whole new set of words are particularly useful, as described in the following sections.

  • Relation. Basically, a relation is a two dimensional table or array containing rows and columns.

  • Relationship. A relationship is the way that data in different tables relate to each other. The relationships, both between the data items forming the various entities in the tables and between the table entities themselves, form the basic core problem of database normalization. There are three basic types of data relationships, and it is important that you have an idea of what they are:

    • One-to-one (1:1). A one-to-one relationship means that each and every instance of any given entity (not just most of them) relates to exactly one instance of another entity. Every person has exactly one right thumbprint that is unique. Every telephone number corresponds to exactly one billable entry for a private individual customer (not a company). Every person in the United States has exactly one Social Security number.

      One-to-many (1:M). A one-to-many relationship means that each instance of a given entity can relate no instances, one instance, or more instances of another entity. Every person has zero biological children, one biological child, or more than one biological child. Every person has zero automobile, one automobile, or more than one automobile.

      Many-to-many (M:N). A many-to-many relationship (zero, one or more instances of a given entity relate to zero, one or many instances of another entity) is a very difficult relationship to directly model, and it is one that is often decomposed into multiple 1:M relationships. Because of blended families, one or more children (siblings, step siblings, half-siblings) can have zero parents (orphaned), one parent (single-parent family), more than one parent (two parents either still together or divorced, or divorced and remarried). A house or property can be deeded to a single person (one in number, not to be confused with unmarried) or more than one person, and these same people (single or multiple in number) can have their names on the deed to more than one house or property.

  • Attribute. An attribute is considered to be a changeable property or characteristic of some component of a program or database that can be set to different values or a column in a relation or table.

  • Tuple. A tuple is an ordered set of values or a set of value attributes in a relational database or a record in a non-relational database: a row in a relation.

  • Deletion anomaly. A deletion anomaly is data inconsistency or unintentional loss of data (or information) due to the deliberate deletion of other data.

  • Insertion anomaly. An insertion anomaly causes an inability to add information to the database due to a lack (either temporary or longer term) or absence of other data.

  • Update anomaly. An update anomaly is data inconsistency due to either data redundancy or the incomplete update of the redundant data.

  • Decomposition of a relation. Decomposition of a relation is splitting a single relation into multiple relations to enable the relation to be in a more normal form.

  • Data redundancy. Data redundancy is unnecessary repetition of data within a database.

  • Data integrity. Data integrity is the consistency of data in the database. It is important to have data integrity so your users know that they can rely on the data to be correct and that the results of their queries and programs will be accurate and expected.

  • Atomic value. An atomic value is a value that is neither a set of values that can be further broken down, nor a repeating group. Each column should be an entire value, but only one value—a value that is not typically broken down into subparts that are used by either the database or the users accessing the information from the database.

  • Referential integrity rule. The referential integrity rule says that the value stored in a non-nullable foreign key must be an actual key value in some relation.

  • Foreign key. A foreign key is a set of attributes (one or more columns) in one relation that is also a key in some (either the same or some other) relation. It is the logical link between relations. A foreign key that references its own relation is referred to as a recursive foreign key.

  • Functional dependency. Functional dependency means that the value of one attribute in a tuple (row) is determined by the value of another attribute in the same tuple. This is almost always the case with the primary key (the piece or pieces of information that makes a tuple unique) and the other information in the tuple. The city and state combination is dependent on the Zip code, even if more than one Zip code can be associated with a city in a given state. The legal identity of a person in the United States is dependent on that person's Social Security number.

  • Determinant. Attribute(s) on the left side of a functional dependency determine the value of other attributes in a tuple (the Zip code determines the city and state; the Social Security number determines the identity of the person; the license number and state determine the automobile ownership).

  • Entity integrity rule. The entity integrity rule says that a key attribute of a row may be null (you have to have a Zip code if you are a city; you have to have a license number and state if you are an automobile being driven on the road).

  • Constraint. A constraint is a rule that restricts the values in a database. Phone number has to be numeric; dollar amounts have to be numeric; state has to be a legal state or province; country has to have been a legal country at one time; date can't be February 31st.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020