Scribd Logo
Upload

Welcome to Scribd!

  • 6 views

    Normalization

    Uploaded by

    vaibhavsharma.vs841
    The document discusses normalization, which is the process of organizing data in a database to minimize redundancy. It describes the different normal forms including 1NF, 2NF, 3NF and their rules to reduce anomalies. Examples are provided to illustrate how tables can be normalized.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Normalization

    Uploaded by

    vaibhavsharma.vs841
    6 views23 pages
    The document discusses normalization, which is the process of organizing data in a database to minimize redundancy. It describes the different normal forms including 1NF, 2NF, 3NF and their rules to reduce anomalies. Examples are provided to illustrate how tables can be normalized.

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses normalization, which is the process of organizing data in a database to minimize redundancy. It describes the different normal forms including 1NF, 2NF, 3NF and their rules to reduce anomalies. Examples are provided to illustrate how tables can be normalized.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    6 views23 pages

    Normalization

    Uploaded by

    vaibhavsharma.vs841
    The document discusses normalization, which is the process of organizing data in a database to minimize redundancy. It describes the different normal forms including 1NF, 2NF, 3NF and their rules to reduce anomalies. Examples are provided to illustrate how tables can be normalized.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 23

    Normalization

    • A large database defined as a single relation


    may result in data duplication. This repetition
    of data may result in:
    • Normalization is the process of organizing the
    data in the database.
    • Normalization is used to minimize the
    redundancy from a relation or set of relations. It
    is also used to eliminate undesirable
    characteristics like Insertion, Update, and
    Deletion Anomalies.
    • Normalization divides the larger table into
    smaller and links them using relationships.
    • The normal form is used to reduce redundancy
    from the database table.
    Why do we need Normalization?
    • The main reason for normalizing the relations
    is removing these anomalies. Failure to
    eliminate anomalies leads to data redundancy
    and can cause data integrity and other
    problems as the database grows.
    Normalization consists of a series of guidelines
    that helps to guide you in creating a good
    database structure.
    • Data modification anomalies can be categorized into
    three types:
    • Insertion Anomaly: Insertion Anomaly refers to when
    one cannot insert a new tuple into a relationship due
    to lack of data.
    • Deletion Anomaly: The delete anomaly refers to the
    situation where the deletion of data results in the
    unintended loss of some other important data.
    • Updatation Anomaly: The update anomaly is when an
    update of a single data value requires multiple rows of
    data to be updated.
    Normal Form Description
    • 1NF A relation is in 1NF if it contains an
    atomic value.
    • 2NF A relation will be in 2NF if it is in 1NF
    and all non-key attributes are fully functional
    dependent on the primary key.
    • 3NF A relation will be in 3NF if it is in 2NF
    and no transition dependency exists.
    Advantages of Normalization
    • Normalization helps to minimize data
    redundancy.
    • Greater overall database organization.
    • Data consistency within the database.
    • Much more flexible database design.
    • Enforces the concept of relational integrity.
    Disadvantages of Normalization
    • You cannot start building the database before
    knowing what the user needs.
    • The performance degrades when normalizing the
    relations to higher normal forms, i.e., 4NF, 5NF.
    • It is very time-consuming and difficult to
    normalize relations of a higher degree.
    • Careless decomposition may lead to a bad
    database design, leading to serious problems.
    First Normal Form (1NF)

    • A relation will be 1NF if it contains an atomic


    value.
    • It states that an attribute of a table cannot
    hold multiple values. It must hold only single-
    valued attribute.
    • First normal form disallows the multi-valued
    attribute, composite attribute, and their
    combinations.
    EMP_ID EMP_NAME EMP_PHONE EMP_STATE

    14 John 7272826385, UP
    9064738238

    20 Harry 8574783832 Bihar

    12 Sam 7390372389, Punjab


    8589830302
    The decomposition of the EMPLOYEE table into 1NF has been shown below:

    EMP_ID EMP_NAME EMP_PHONE EMP_STATE

    14 John 7272826385 UP
    14 John 9064738238 UP
    20 Harry 8574783832 Bihar
    12 Sam 7390372389 Punjab
    12 Sam 8589830302 Punjab
    Second Normal Form
    • To be in second normal form, a relation must be in
    first normal form and relation must not contain
    any partial dependency.
    • A relation is in 2NF if it has No Partial
    Dependency, i.e., no non-prime attribute
    (attributes which are not part of any candidate
    key) is dependent on any proper subset of any
    candidate key of the table.
    • Partial Dependency – If the proper subset of
    candidate key determines non-prime attribute, it
    is called partial dependency.
    2 NF
    • In the 2NF, relational must be in 1NF.
    • In the second normal form, all non-key
    attributes are fully functional dependent on
    the primary key
    • Example: Let's assume, a school can store the
    data of teachers and the subjects they teach.
    In a school, a teacher can teach more than
    one subject.
    Example: Let's assume, a school can store the
    data of teachers and the subjects they teach. In
    a school, a teacher can teach more than one
    subject. TEACHER table

    TEACHER_ID SUBJECT TEACHER_AGE

    25 Chemistry 30
    25 Biology 30
    47 English 35
    83 Math 38
    83 Computer 38
    • In the given table, non-prime attribute
    TEACHER_AGE is dependent on TEACHER_ID
    which is a proper subset of a candidate key.
    That's why it violates the rule for 2NF.
    • To convert the given table into 2NF, we
    decompose it into two tables:
    • TEACHER_DETAIL table:

    TEACHER_ID TEACHER_AGE

    25 30
    47 35
    83 38

    TEACHER_SUBJECT table: TEACHER_ID SUBJECT

    25 Chemistry
    25 Biology
    47 English
    83 Math
    83 Computer
    Third Normal Form (3NF)

    • A relation will be in 3NF if it is in 2NF and not


    contain any transitive partial dependency.
    • 3NF is used to reduce the data duplication. It
    is also used to achieve the data integrity.
    • If there is no transitive dependency for non-
    prime attributes, then the relation must be in
    third normal form.
    • A relation is in third normal form if it holds
    atleast one of the following conditions for
    every non-trivial function dependency X → Y.
    • X is a super key.
    • Y is a prime attribute, i.e., each element of Y is
    part of some candidate key.
    Example:
    • EMPLOYEE_DETAIL table:

    EMP_ID EMP_NA EMP_ZIP EMP_STA EMP_CIT


    ME TE Y

    222 Harry 201010 UP Noida


    333 Stephan 02228 US Boston
    444 Lan 60007 US Chicago
    555 Katharine 06389 UK Norwich
    666 John 462007 MP Bhopal
    Super key in the table above:
    1.{EMP_ID}, {EMP_ID, EMP_NAME}, {EMP_ID, EMP_NAME, EMP_ZIP}
    ....so on
    • Candidate key: {EMP_ID}
    • Non-prime attributes: In the given table, all
    attributes except EMP_ID are non-prime.
    • Here, EMP_STATE & EMP_CITY dependent on
    EMP_ZIP and EMP_ZIP dependent on EMP_ID.
    The non-prime attributes (EMP_STATE,
    EMP_CITY) transitively dependent on super
    key(EMP_ID). It violates the rule of third
    normal form.
    • That's why we need to move the EMP_CITY and EMP_STATE
    to the new <EMPLOYEE_ZIP> table, with EMP_ZIP as a
    Primary key.
    EMPLOYEE table:

    EMP_ID EMP_NAME EMP_ZIP

    222 Harry 201010


    333 Stephan 02228
    444 Lan 60007
    555 Katharine 06389
    666 John 462007
    EMPLOYEE_ZIP table:

    EMP_ZIP EMP_STATE EMP_CITY

    201010 UP Noida
    02228 US Boston
    60007 US Chicago
    06389 UK Norwich
    462007 MP Bhopal
    Advantages of Normal Form
    • Reduced data redundancy: Normalization helps to eliminate duplicate data in
    tables, reducing the amount of storage space needed and improving database
    efficiency.
    • Improved data consistency: Normalization ensures that data is stored in a
    consistent and organized manner, reducing the risk of data inconsistencies and
    errors.
    • Simplified database design: Normalization provides guidelines for organizing
    tables and data relationships, making it easier to design and maintain a database.
    • Improved query performance: Normalized tables are typically easier to search and
    retrieve data from, resulting in faster query performance.
    • Easier database maintenance: Normalization reduces the complexity of a database
    by breaking it down into smaller, more manageable tables, making it easier to add,
    modify, and delete data.
    • Overall, using normal forms in DBMS helps to improve data quality, increase
    database efficiency, and simplify database design and maintenance.

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy