RDBMS & CODDS RULES..

Vedapriya Jayaramareddy
ITP Group(BO1)
Copyright 2007 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture.

Data Models.

A data model is a model that describes in an

abstract way how data is represented in a business
organization, an information system or a database
management system.

There are basically 3 classic data models

1. Hierarchical Data Model
2. Network Data Model
3. Relational Data Model

Copyright 2007 Accenture All R

Type of Data Model

Description

Hierarchical Model

Well suited for data which

are related hierarchically

Network Model

Database model conceived

as flexible way of
representing objects and
their relationships

Relational Model

Data is represented in the

form of two dimensional
tables

Copyright 2007 Accenture All R

Features Of Relational
Model
The relational model of data permits the database
designer to create a consistent, logical representation
of information.
The basic principle of the relational model is the
Information Principle: all information is represented by
data values in relations.
Database Management Systems must adhere to
Codds rules to be termed as RDBMS.
Copyright 2007 Accenture All R

RDBMS.

A relational database management system

(RDBMS) uses matching values in multiple tables to
relate to the information in one table with the
information in the other table.

The two most prominent characteristics of a

relational database are
1. Data stored in tables
2. Relationships between tables

Copyright 2007 Accenture All R

Who Is Dr. CODD?

An IBM researcher.
Developed the relational data model in 1970.
Published a list of 12 rules that defined an ideal
RDBMS.

Copyright 2007 Accenture All R

Codds Rules..
No commercial RDBMS fully conforms to all 12 rules.
The rules are so strict that all popular so called
relational DBMSs fail on many of the criteria.
In practice, many database products (for ex. Oracle,
Sybase etc..) are considered relational even if they do
not strictly adhere to all 12 rules.

Copyright 2007 Accenture All R

Lets begin..

Rule 1: The Information Rule :

1. All data should be presented to the user in table

form.
2. All information in the database to be represented in
one and only one way, Namely by values in column
positions within rows of tables.

Copyright 2007 Accenture All R

Rule 2.

Guaranteed Access Rule :

Each piece of data (atomic data) must be logically

accessible by referencing
1. A table
2. A primary or unique key value and
3. A column

Copyright 2007 Accenture All R

Rule 3.

Systematic Treatment Of Null Values :

The DBMS must allow each field to remain null (or

empty).
Null must always be interpreted as an unknown
value.

Copyright 2007 Accenture All R

10

Rule 4
Dynamic Online Catalog based on the
relational model :
Users must be able to access the databases structure
(catalog) using the same query language that they use
to access the databases data.

Copyright 2007 Accenture All R

11

Rule 5
Comprehensive Data Sublanguage Rule :
There must be a single language that handles all
communication with the database management
system.
Every RDBMS should provide a language to allow the
user to query and manipulate the contents of the
RDBMS.

Copyright 2007 Accenture All R

12

Rule 6
View Updating Rule :
All views that are theoretically updatable must be
updatable by the system.
Views are virtual tables or abstractions of the source
tables.

Copyright 2007 Accenture All R

13

Rule 7
High-level insert, update and delete :
The system must support set-at-a-time INSERT,
UPDATE, and DELETE operators.

Copyright 2007 Accenture All R

14

Rule 8
Physical Data Independence :
Applications that access data in a relational database
must be unaffected by changes in the way the data is
physically stored.

Copyright 2007 Accenture All R

15

Rule 9
Logical Data Independence :
The database schema or structure of tables (logical) &
relationships can change without having to recreate
the application that uses it.
Difficult to satisfy.

Copyright 2007 Accenture All R

16

Rule 10
Integrity Independence :
Integrity constraints specific to a particular relational
database must be stored separately from application
programs and stored in the catalog.
It must be possible to change such constraints as &
when appropriate without unnecessarily affecting
existing applications.
Copyright 2007 Accenture All R

17

Rule 11
Distribution Independence :
A relational DBMS has distribution independence.
The RDBMS may spread across more than one
system & across several networks, however to the
end-user the tables should appear no different to those
that are local.

Copyright 2007 Accenture All R

18

Rule 12
Non Subversion Rule :
No way to modify the database structure other than
through the multiple row database language.

Copyright 2007 Accenture All R

19

Thank You!

Copyright 2007 Accenture All R

20