Unnormalized form

In database normalization, unnormalized form (UNF or 0NF), also known as an unnormalized relation or non-first normal form (N1NF or NF²),^[1] is a database data model (organization of data in a database) which does not meet any of the conditions of database normalization defined by the relational model. Database systems which support unnormalized data are sometimes called non-relational or NoSQL databases. In the relational model, unnormalized relations can be considered the starting point for a process of normalization.

"Unnormalized form" should not be confused with denormalization, where normalization is deliberately compromised for selected tables in a relational database.

History[edit]

In 1970, E. F. Codd proposed the relational data model, now^[when?] widely accepted as the standard data model.^[2] At that time, office automation was the major use of data storage systems, which resulted in the proposal of many UNF/NF² data models like the Schek model, Jaeschke models (non-recursive and recursive algebra), and the nested table data model (NTD).^[1] IBM organized the first international workshop exclusively on this topic in 1987 which was held in Darmstadt, Germany.^[1] Moreover, a lot of research has been done and journals have been published to address the shortcomings of the relational model. Since the turn of the millennium, NoSQL databases have become popular owing to the demands of Web 2.0.

Relational form[edit]

Normalization to first normal form requires the initial data to be viewed as relations.^[3] In database systems relations are represented as tables. The relation view implies some constraints on the tables:

• No duplicate rows. In practice, this is ensured by defining one or more columns as primary keys.
• Rows do not have an intrinsic order. While tables have to be stored and presented in some order, this is unstable and implementation dependent. If a specific ordering needs to be represented, it has to be in the form of data, e.g. a "number" column.
• Columns have unique names within the same table.
• Each column has a domain (or data type) which defines the allowed values in the column.
• All rows in a table have the same set of columns.

This definition does not preclude columns having sets or relations as values, e.g. nested tables. This is the major difference to first normal form.

NoSQL databases like document databases typically does not conform to the relational view. For example, an JSON or XML database might support duplicate records and intrinsic ordering. Such database can be described as non-relational. But there are also database models which support the relational view, but does not embrace first normal form.^[4] Such models are called non-first normal form relations (abbreviated NFR, N1NF or NF²).

Example with a table valued column[edit]

This table represent a relation where one of the columns (Transactions) is itself relation-valued. This is a valid relation but does not conform to first normal form which does not allow nested relations. The table is therefore unnormalized.

Modern applications[edit]

As of 2016, companies like Google, Amazon and Facebook deal with large amounts of data that are difficult to store efficiently. They use NoSQL databases, which are based on the principles of the unnormalized relational model, to deal with the storage issue.^[5] Some examples of NoSQL databases are MongoDB, Apache Cassandra and Redis. These databases are more scalable and easier to query with as they do not involve expensive operations like JOIN.^{[citation needed]}

See also[edit]

• Denormalization
• Normalization
• First normal form
• Second normal form
• Third normal form
• Boyce–Codd normal form
• NoSQL

References[edit]