Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Lernen Third Normal Form | Normalisierung und Normalformen
Relationale Datenbank und Normalisierung

Third Normal Form

Swipe um das Menü anzuzeigen

Third Normal Form (3NF):

  • The table must already follow the rules of Second Normal Form (2NF).
  • Every column should depend only on the primary key, not on other non-key columns.
  • If a column depends on another non-key column, move it to a separate table.

Sometimes, you may want to add a new attribute to a table. However, this can significantly increase the table’s size, especially if the attribute is not related to the primary key. In such cases, adding it is not a logical design choice. Consider this example:

ThirdNF Bad%404x-8

In this case, Designer Grade and Designer Country are not true attributes of the Project, they belong to the Designer instead. As in the previous example, if we delete the first row, we would lose important information about Robert Jarry’s grade and country, which indicates poor table design. It’s time to normalize!

Project and Designer tables

Great! You now have separate tables for each entity: the Project table contains only project-related attributes, while the Designer table stores attributes specific to the designer.

question mark

What are the rules of the Third Normal Form?

Wählen Sie alle richtigen Antworten aus

War alles klar?

Wie können wir es verbessern?

Danke für Ihr Feedback!

Abschnitt 3. Kapitel 4

Fragen Sie AI

expand

Fragen Sie AI

ChatGPT

Fragen Sie alles oder probieren Sie eine der vorgeschlagenen Fragen, um unser Gespräch zu beginnen

Abschnitt 3. Kapitel 4
some-alt