SUBMITTED TO:Ma’am Misbah

SUBMITTED BY: Huma

ROLL NO: info.tech-16008

DEPARTMENT: BS IT

SEMETER: (5)
 Codd 12 Rules
Codd 12 rules are a set of thirteen rules (numbered zero totwelve) proposed by
Edgar F. Codd, was a computer scientist while working for IBM. He invented the
relational model for database management (theoretical basis for relational
databases).said that if a Database Management System meets these rules, it can be
called as a Relational Database Management System(RDBMS).

Rule Zero
The system must qualify as relational, as a database, and as a management system.
For a system to qualify as a relational database management system (RDBMS),
that system must use its relational facilities (exclusively) to manage the database.

The other 12 rules derive from this rule. The rules are as follows:

Rule 1

Information rule
This rule states that all information (data), which is stored in the database, must be
a value of some table cell. Everything in a database must be stored in table formats.
This information can be user data or meta-data.

Rule 2

The guaranteed access rule

All data must be accessible. This rule is essentially a restatement of the

fundamental requirement for primary keys. It says that every individual scalar
value in the database must be logically addressable by specifying the name of the
containing table, the name of the containing column and the primary key value of
the containing row.

Rule 3

Systematic Treatment of NULL values

This rule states the NULL values in the database must be given a systematic
treatment. As a NULL may have several meanings, i.e. NULL can be interpreted as
one the following: data is missing, data is not known, data is not applicable etc.

Rule 4

Active Online Catalog

The system must support an online, inline, relational catalog that is accessible to
authorized users by means of their regular query language. That is, users must be
able to access the databases structure (catalog) using the same query language that
they use to access the databases data.

Rule 5

Comprehensive Data Sub-Language Rule

The comprehensive data sub language rule: The system must support at least one
relational language that

1. Has a linear syntax

2. Can be used both interactively and within application programs,

3. Supports data definition operations (including view definitions), data

manipulation operations (update as well as retrieval), security and integrity
constraints, and transaction management operations (begin, commit, and rollback).

Rule 6
View Updating Rule
All the views of a database, which can theoretically be updated, must also be
updatable by the system.

Rule 7

High-level insert, update, and delete Rule

The system must support set-at-a-time insert, update, and delete operators. This
means that data can be retrieved from a relational database in sets constructed of
data from multiple rows and/or multiple tables. This rule states that insert, update,
and delete operations should be supported for any retrievable set rather than just
for a single row in a single table.

Rule 8

Physical Data Independence

The data stored in a database must be independent of the applications that access
the database. Any change in the physical structure of a database must not have any
impact on how the data is being accessed by external applications.
Rule 9
Logical Data Independence
The logical data in a database must be independent of its user’s view
(application). Any change in logical data must not affect the applications using it.
Changes to the logical level (tables, columns, rows, and so on) must not require a
change to an application based on the structureFor example, if two tables are
merged or one is split into two different tables, there should be no impact or
change on the user application. This is one of the most difficult rule to apply.

Rule 10

Integrity Independence

A database must be independent of the application that uses it. All its integrity
constraints can be independently modified without the need of any change in the
application.Integrity constraints must be specified separately from application
programs and stored in the catalog. This rule makes a database independent of the
front-end application and its interface.

Rule 11

Distribution independence

The distribution of portions of the database to various locations should be invisible

to users of the database. Existing applications should continue to operate
successfully:

1. When a distributed version of the DBMS is first introduced.

2. When existing distributed data are redistributed around the system.

Rule 12

Non-subversion rule

This rule states that if a system has an interface that provides access to low level
records, this interface then must not be able to subvert the system and bypass
security and integrity constraints.