top-rated free essay

Normalization Process

By AMELIAELIZA May 25, 2013 1486 Words
The normalization process is used by database developers to design databases in which it is easy to organize and manage data while ensuring the accuracy of data throughout the database. The advantages and disadvantages of both normalization and denormalization of a database are discussed, as well as data integrity versus performance issues that pertain to normalization. The highlights of this hour include

* What normalization is
* Benefits of normalization
* Advantages of denormalization
* Normalization techniques
* Guidelines of normalization
* The three normal forms
* Database design
Normalizing a Database
Normalization is a process of reducing redundancies of data in a database. Normalization is a technique that is used when designing and redesigning a database. Normalization is a process or set of guidelines used to optimally design a database to reduce redundant data. The actual guidelines of normalization, called normal forms, will be discussed later in this hour. It was a difficult decision to decide whether to cover normalization in this book because of the complexity involved in understanding the rules of the normal forms this early on in your SQL journey. However, normalization is an important process that, if understood, will increase your understanding of SQL. We have attempted to simplify the process of normalization as much as possible in this hour. At this point, don't be overly concerned with all the specifics of normalization; it is most important to understand the basic concepts. The Raw Database

A database that is not normalized may include data that is contained in one or more different tables for no apparent reason. This could be bad for security reasons, disk space usage, speed of queries, efficiency of database updates, and, maybe most importantly, data integrity. A database before normalization is one that has not been broken down logically into smaller, more manageable tables. Figure 4.1 illustrates the database used for this book before it was normalized.

Logical Database Design
Any database should be designed with the end user in mind. Logical database design, also referred to as the logical model, is the process of arranging data into logical, organized groups of objects that can easily be maintained. The logical design of a database should reduce data repetition or go so far as to completely eliminate it. After all, why store the same data twice? Naming conventions used in a database should also be standard and logical.

The needs of the end user should be one of the top considerations when designing a database. Remember that the end user is the person who ultimately uses the database. There should be ease of use through the user's front-end tool (a client program that allows a user access to a database), but this, along with optimal performance, cannot be achieved if the user's needs are not taken into consideration. Some user-related design considerations include the following: * What data should be stored in the database?

* How will the user access the database?
* What privileges does the user require?
* How should the data be grouped in the database?
* What data is the most commonly accessed?
* How is all data related in the database?
* What measures should be taken to ensure accurate data? Data Redundancy
Data should not be redundant, which means that the duplication of data should be kept to a minimum for several reasons. For example, it is unnecessary to store an employee's home address in more than one table. With duplicate data, unnecessary space is used. Confusion is always a threat when, for instance, an address for an employee in one table does not match the address of the same employee in another table. Which table is correct? Do you have documentation to verify the employee's current address? As if data management were not difficult enough, redundancy of data could prove to be a disaster. The Normal Forms

The next sections discuss the normal forms, an integral concept involved in the process of database normalization. Normal form is a way of measuring the levels, or depth, to which a database has been normalized. A database's level of normalization is determined by the normal form. The following are the three most common normal forms in the normalization process: * The first normal form

* The second normal form
* The third normal form
Of the three normal forms, each subsequent normal form depends on normalization steps taken in the previous normal form. For example, to normalize a database using the second normal form, the database must first be in the first normal form.

The First Normal Form
The objective of the first normal form is to divide the base data into logical units called tables. When each table has been designed, a primary key is assigned to most or all tables. Examine Figure 4.2, which illustrates how the raw database shown in the previous figure has been redeveloped using the first normal form.

The Second Normal Form
The objective of the second normal form is to take data that is only partly dependent on the primary key and enter that data into another table. Figure 4.3 illustrates the second normal form.

The Third Normal Form
The third normal form's objective is to remove data in a table that is not dependent on the primary key. Figure 4.4 illustrates the third normal form.

Benefits of Normalization
Normalization provides numerous benefits to a database. Some of the major benefits include the following : * Greater overall database organization
* Reduction of redundant data
* Data consistency within the database
* A much more flexible database design
* A better handle on database security
Organization is brought about by the normalization process, making everyone's job easier, from the user who accesses tables to the database administrator (DBA) who is responsible for the overall management of every object in the database. Data redundancy is reduced, which simplifies data structures and conserves disk space. Because duplicate data is minimized, the possibility of inconsistent data is greatly reduced. For example, in one table an individual's name could read STEVE SMITH, whereas the name of the same individual reads STEPHEN R. SMITH in another table. Because the database has been normalized and broken into smaller tables, you are provided with more flexibility as far as modifying existing structures. It is much easier to modify a small table with little data than to modify one big table that holds all the vital data in the database. Lastly, security is also provided in the sense that the DBA can grant access to limited tables to certain users. Security is easier to control when normalization has occurred.

Drawbacks of Normalization
Although most successful databases are normalized to some degree, there is one substantial drawback of a normalized database: reduced database performance. The acceptance of reduced performance requires the knowledge that when a query or transaction request is sent to the database, there are factors involved, such as CPU usage, memory usage, and input/output (I/O). To make a long story short, a normalized database requires much more CPU, memory, and I/O to process transactions and database queries than does a denormalized database. A normalized database must locate the requested tables and then join the data from the tables to either get the requested information or to process the desired data. A more in-depth discussion concerning database performance occurs in Hour 18, "Managing Database Users." Denormalizing a Database

Denormalization is the process of taking a normalized database and modifying table structures to allow controlled redundancy for increased database performance. Attempting to improve performance is the only reason to ever denormalize a database. A denormalized database is not the same as a database that has not been normalized. Denormalizing a database is the process of taking the level of normalization within the database down a notch or two. Remember, normalization can actually slow performance with its frequently occurring table join operations. (Table joins are discussed during Hour 13, "Joining Tables in Queries.") Denormalization may involve recombining separate tables or creating duplicate data within tables to reduce the number of tables that need to be joined to retrieve the requested data, which results in less I/O and CPU time.

Summary
A difficult decision has to be made concerning database design—to normalize or not to normalize, that is the question. You will always want to normalize a database to some degree. How much do you normalize a database without destroying performance? The real decision relies on the application itself. How large is the database? What is its purpose? What types of users are going to access the data? This hour covered the three most common normal forms, the concepts behind the normalization process, and the integrity of data. The normalization process involves many steps, most of which are optional but vital to the functionality and performance of your database. Regardless of how deep you decide to normalize, there will most always be a trade-off, either between simple maintenance and questionable performance or complicated maintenance and better performance.

Cite This Document

Related Documents

  • The Process of Normalization to Reduce Data Redundancy

    ...Data Ware House Normalization it’s a process of splitting data into 2 or more entities to reduce data redundancy. Normal Forms: 1. A database table must contain no repeating groups 2. All non-key attributes of a table must rely on the entire key of the table. 3. All non-key fields must depend solely on the table’s primary key. First Bu...

    Read More
  • Database Normalization and Logical Process Concept Paper

    ...Database Normalization and Logical Process Concept paper This short paper will explain with a simple example the process and the need of normalization in the most of the business databases. Complete proposal break down (Timeline phases, Financial phases) will be submitted per management request. Overview At first any database should be design...

    Read More
  • Database Normalization

    ...Normalization Normalization is a method for organizing data elements in a database into tables. Normalization Avoids • Duplication of Data – The same data is listed in multiple lines of the database • Insert Anomaly – A record about an entity cannot be inserted into the table without first inserting information about an...

    Read More
  • Database Normalization

    ... Normalization A logical design method which minimizes data redundancy and reduces design flaws. Consists of applying various “normal” forms to the database design. The normal forms break down large tables into smaller subsets. First Normal Form (1NF) Each attribute must be atomic • No repeating columns within a row. ...

    Read More
  • Dictionary and Normalization Guidelines

    ...CSS/559 – Data Base Concepts II Data Dictionary and Normalization Guidelines The purpose of a data dictionary is to define the objects and data within an organization's database management system. This metadata does not contain any of the database's data, but only information about the structure, storage and use of the database's data. A ...

    Read More
  • Normalization of Database Management Systems

    ...Normalization of Database Tables Database Tables and Normalization * Normalization is a process for assigning attributes to entities. It reduces data redundancies and helps eliminate the data anomalies. * Normalization works through a series of stages called normal forms: * First normal form (1NF) * Second normal form...

    Read More
  • Database Design Process

    ...up with a design that reflects the business you are trying to model. This paper shows describes design process of database project. The importance of Completing the Design Process An important point to keep in mind is that the level of structural integrity and data integrity is in direct proportion to how thoroughly the design process is follo...

    Read More
  • Process Flowchart

    ... Process Flowchart Process Flowchart This paper includes information about a process (University of Phoenix, 2010, Syllabus) completed daily. A flowchart represents activities in a process. A flowchart is also included in this paper. A key element of operations strategy is the activities involved in process design (Chase, Jacobs...

    Read More

Discover the Best Free Essays on StudyMode

Conquer writer's block once and for all.

High Quality Essays

Our library contains thousands of carefully selected free research papers and essays.

Popular Topics

No matter the topic you're researching, chances are we have it covered.