Database paradigm:
The construction database must follow certain rules. In a relational database, this rule is the paradigm.
A paradigm is a collection of relational patterns that conform to a certain level. Relationships in relational databases must meet certain requirements, that is, to meet different paradigms.
The paradigm that satisfies the minimum requirements is the first paradigm. On the basis of the first paradigm, further satisfying more requirements is called the second paradigm, and the rest of the paradigms are based on the second analogy. In general, the database simply satisfies the third paradigm.
First normal form (1NF):
In any relational database, the first paradigm (1NF) is the basic requirement for relational schemas, and a database that does not meet the first normal form (1NF) is not a relational database.
The so-called First paradigm (1NF) refers to the fact that each column of a database table is an indivisible basic data item and cannot have multiple values in the same column, that is, an attribute in an entity cannot have multiple values or cannot have duplicate properties.
The first paradigm is a column with no duplicates.
Second Normal form (2NF):
The second paradigm is established on the basis of the first paradigm, that is, satisfying the second paradigm must first satisfy the first paradigm. The second paradigm requires that each instance or row in a database table must be divided by a unique region. It is often necessary to add a column to the table to store the unique identity of each instance.
The second paradigm is that a non-principal attribute is dependent on the primary key.
Third paradigm (3NF):
Satisfying the third paradigm must first satisfy the second paradigm. In short, the third paradigm requires that a database table not contain non-primary key information already contained in other tables.
The third paradigm is that attributes do not depend on other non-principal properties.
SQL Server Paradigm