Introduction to Database | Relational Data Structures

Running head: Introduction to Database
INTRODUCTION TO DATABASE
Name of the Student
Name of the University
Author Note

Introduction to Database1
Table of Contents
1. Relational data structures....................................................................................................2
A relational database schema that translates your relational data structures:............................8
Bibliography:............................................................................................................................13

Introduction to Database2
1. Relational data structures
Employees Entity:
Employees (EmployeeID,  EmpName, Phonenumber, departmentID, StoreNumber)
1nf:
When a relation contains multi-valued or composite attribute, it will violate the first
normal form. But employee table does not contain any composite or multi-valued attribute.
2nf:
A relation must be in first 1nf and it must not contain partial dependency. Employee
tables does not contain any partial dependency.
3nf:
There is no transitive dependency for non-prime attributes are present in the employee
table thus, this table is in third normal form.
Department Entity:
Department (DepartmentID,  DepartmentName)
1nf:
When a relation contains multi-valued or composite attribute, it will violate the first
normal form. But department table does not contain any composite or multi-valued attribute.
2nf:
A relation must be in first 1nf and it must not contain partial dependency. Department
tables does not contain any partial dependency.
3nf:

Introduction to Database3
There is no transitive dependency for non-prime attributes are present in the
department table thus, this table is in third normal form.
Customer Entity:
Customer (CustomerID,  Firstname, lastName, StreetAddress, Town, State, PostCode,
workNumber, HomeNumber)
1nf:
When a relation contains multi-valued or composite attribute, it will violate the first
normal form. But customer table does not contain any composite or multi-valued attribute.
2nf:
A relation must be in first 1nf and it must not contain partial dependency. Customer
tables does not contain any partial dependency.
3nf:
There is no transitive dependency for non-prime attributes are present in the customer
table thus, this table is in third normal form.
Complaint Entity:
Complaint (ComplaintNumber  ComplaintDate, ComplaintType, status, EmployeeID,
CustomerID)
1nf:
When a relation contains multi-valued or composite attribute, it will violate the first
normal form. But complaint table does not contain any composite or multi-valued attribute.
2nf: