Scribd
Upload
21 views2 pages

The Relational Model

The document discusses the relational model for portraying data in tables and its strengths in linking tables. It describes properly designed relational tables with unique primary keys and normalized attributes. It outlines the six phases of database design including identifying entities, constructing entity relationships, adding keys and attributes, normalization, constructing physical tables, and preparing user views. It also describes three types of anomalies - insertion, deletion, and update anomalies.

Uploaded by

Bella Ayab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
21 views2 pages

The Relational Model

The document discusses the relational model for portraying data in tables and its strengths in linking tables. It describes properly designed relational tables with unique primary keys and normalized attributes. It outlines the six phases of database design including identifying entities, constructing entity relationships, adding keys and attributes, normalization, constructing physical tables, and preparing user views. It also describes three types of anomalies - insertion, deletion, and update anomalies.

Uploaded by

Bella Ayab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

The Relational Model

-portrays data in the form of two dimensional 'tables'

-It's strength is the ease with which tables may be linked to one another

-Properly Designed Relational Tables

Properly Designed Relational Tables

-each row in table must be unique in at least one attribute, which is the primary key

-tables must conform to the rules of normalization (i.e., free from structural dependencies or anomalies)

6 phases of database design ("view modeling")

1) Identify entities
view modeling begins by identifying the primary entities of the business function in question
2) Construct a data model showing entity associations (Cardinality)
to determine the associations between entities and document them with an ER diagram
3) Add primary keys and attributes to the model
Add primary keys: analyst should select a primary key that logically defines the nonkey attributes and uniquely
identifies each occurrence in the entity

Add attributes: every attribute in an entity should appear directly or indirectly (a calculated value) in one or
more user views

4) Normalize the data model and add foreign keys


Normalization issues that needed resolution:
1) Repeating group data in purchase order
2) Repeating group data in receiving report
3) Transitive dependencies

5) Construct the physical database

create the physical tables and populate them with data

5) Prepare the user view


report program is used to make the view visually attractive and easy to use

3 Types of Anomalies
1) Insertion anomaly
a new item cannot be added to the table until at least one entity uses a particular attribute item

accountants and data normalization- can result in unrecorded transactions and incomplete audit trails
2) Deletion anomaly
if an attribute item used by only one entity is deleted, all information about that attribute item is lost
-involves the unintentional deletion of data from a table

accountants and data normalization- can cause the loss of accounting records and the destruction of audit
trails
3) Update anomaly
a modification on an attribute must be made in each of the rows in which the attribute appears
-results from data redundancy in an unnormalized table
accountants and data normalization- can generate conflicting and obsolete database values

You might also like