chapter
    Functional Dependencies, Keys and Normalization Notes for GATE CS

    Functional Dependencies, Keys and Normalization notes for GATE CS: 35 study cards covering concepts, formulas, shortcuts and exam traps, plus solved practice

    functional dependencies keys and normalization notes

    Chapter Roadmap: Functional Dependencies, Keys and Normalization

    Databases › Functional Dependencies, Keys and Normalization

    Chapter Journey

    Three topics that form the backbone of relational database theory.

    1
    Functional Dependency Inference and Armstrong's Axioms
    The logical rules for deriving new dependencies from a given set. You are here.
    5 PYQs
    2
    Candidate Keys, Closures and Superkeys
    Using attribute closures to find all candidate keys and count superkeys.
    2 PYQs
    3
    Normal Forms, Lossless Decomposition and Dependency Preservation
    1NF through BCNF, checking whether a decomposition loses data or dependencies.
    6 PYQs

    What Is a Functional Dependency?

    What Is a Functional Dependency?

    A **Functional Dependency (FD)** is a constraint between two sets of attributes in a relation.

    Definition
    holds on a relation if, for every valid instance of , any two tuples that agree on all attributes of also agree on all attributes of .
    In plain English: If you know the value of , you can uniquely determine the value of .
    Determinant ()
    The attribute(s) you already know
    Dependent ()
    The attribute(s) you can deduce
    Key point: An FD is a statement about all possible valid instances of the relation, not just the rows you currently see in a table.

    Trivial vs Non-Trivial Functional Dependencies

    Trivial vs Non-Trivial FDs

    Trivial FD
    where
    The right side is already inside the left side. Always true. No real information.
    Ex: ,
    Non-Trivial FD
    where
    Right side has at least one new attribute. Carries genuine information.
    Ex:
    Completely Non-Trivial
    Left and right sides share no attributes. Often called "useful" in exams.

    32 more cards in this chapter

    Free preview ends here

    Login to view the complete notes

    Creating an account is free. You get the rest of this chapter, step-by-step solutions, and a study plan built around the topics you are actually weak at.

    Why MastersUp

    Personalised first. High quality throughout.

    Most platforms hand everyone the same content. Here the content moves with your performance, topic by topic.

    Built around you, not around a syllabus PDF

    Every answer you give moves your topic-level intelligence rate. The next question, the next revision card and tomorrow's plan all change with it.

    Revision that hits your weak spots

    We only revise topics you have actually attempted and are still below the safe bar on — never the same chapter on repeat.

    Questions calibrated to the real exam

    Each question carries a measured toughness. You are served a rung above your current level, so practice keeps stretching you.

    Notes written for recall, not for volume

    Full lesson cards for first study, curated short-note cards for the last mile — with derivations, traps and exam patterns marked.

    One place for everything

    Notes, chapter practice, previous-year questions, test series and full-length papers — all feeding one picture of your preparation.

    Honest progress

    No vanity streaks. Progress here means chapters mastered and accuracy that held up on harder questions.

    Unlock the whole course

    Full notes and short notes, the complete question bank with worked solutions, mock tests, full-length papers, and an adaptive plan that rebuilds itself as you improve.

    Functional Dependencies, Keys and Normalization Notes for GATE CS

    Functional Dependencies, Keys and Normalization notes for GATE CS: 35 study cards covering concepts, formulas, shortcuts and exam traps, plus solved practice questions.

    Chapter Roadmap: Functional Dependencies, Keys and Normalization

    Databases › Functional Dependencies, Keys and Normalization

    Chapter Journey

    Three topics that form the backbone of relational database theory.

    1
    Functional Dependency Inference and Armstrong's Axioms
    The logical rules for deriving new dependencies from a given set. You are here.
    5 PYQs
    2
    Candidate Keys, Closures and Superkeys
    Using attribute closures to find all candidate keys and count superkeys.
    2 PYQs
    3
    Normal Forms, Lossless Decomposition and Dependency Preservation
    1NF through BCNF, checking whether a decomposition loses data or dependencies.
    6 PYQs

    What Is a Functional Dependency?

    What Is a Functional Dependency?

    A **Functional Dependency (FD)** is a constraint between two sets of attributes in a relation.

    Definition
    holds on a relation if, for every valid instance of , any two tuples that agree on all attributes of also agree on all attributes of .
    In plain English: If you know the value of , you can uniquely determine the value of .
    Determinant ()
    The attribute(s) you already know
    Dependent ()
    The attribute(s) you can deduce
    Key point: An FD is a statement about all possible valid instances of the relation, not just the rows you currently see in a table.

    Trivial vs Non-Trivial Functional Dependencies

    Trivial vs Non-Trivial FDs

    Trivial FD
    where
    The right side is already inside the left side. Always true. No real information.
    Ex: ,
    Non-Trivial FD
    where
    Right side has at least one new attribute. Carries genuine information.
    Ex:
    Completely Non-Trivial
    Left and right sides share no attributes. Often called "useful" in exams.

    Armstrong's Axioms: The Three Core Rules

    Armstrong's Axioms

    Three inference rules for deriving new FDs from a given set . They are sound (never derive false FDs) and complete (can derive all true FDs).

    1. Reflexivity
    If , then
    2. Augmentation
    If , then for any
    3. Transitivity
    If and , then
    Why these matter: Together, soundness and completeness mean these three rules are all you need to reason about functional dependencies. Every other rule is a shortcut derived from these three.

    More notes in this unit