normalization for tables, Study notes of Database Programming

normalization for tables and checking is it 1NF or 2NF or 3NF

Typology: Study notes

2018/2019

Uploaded on 04/01/2019

b2b2
b2b2 🇸🇦

3 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Candy Database
Employees
Q1:
This relation is in 1NF
Because no repeating groups, No multivalued attribute, No composite attributes, No
nested relations
Q2:
This relation in 2NF
Because full functional
E-no
--------->E-name, E-phone, E-super, gender, E-Nationality, E-address, Age,
period, B-no, C-name
Q3:
This relation in 3NF
Because no transitive
Worktime
Q1:
This relation is in 1NF
Because no repeating groups, No multivalued attribute, No composite attributes, No
nested relation
Q2:
This relation in 2NF
Because full functional.
Period
----> From, To
Q3:
This relation in 3NF
Because no transitive
pf3
pf4

Partial preview of the text

Download normalization for tables and more Study notes Database Programming in PDF only on Docsity!

Candy Database

Employees

Q1:

This relation is in 1NF Because no repeating groups, No multivalued attribute, No composite attributes, No nested relations Q2: This relation in 2NF Because full functional E-no (^) --------->E-name, E-phone, E-super, gender, E-Nationality, E-address, Age, period, B-no, C-name Q3: This relation in 3NF Because no transitive

Worktime

Q1:

This relation is in 1NF Because no repeating groups, No multivalued attribute, No composite attributes, No nested relation Q2: This relation in 2NF Because full functional. Period ----> From, To Q3: This relation in 3NF Because no transitive

Branch Q1: This relation is 1NF Because no repeating groups, No multivalued attribute, No composite attributes, No nested relations Q2: This relation is 2NF Because no partial dependencies Q3: This relation is 3NF Because no transitive dependencies Career Q1: This relation is 1NF Because no repeating groups, No multivalued attribute, No composite attributes, No nested relations Q2: This relation is 2NF Because no partial dependencies CareerName ----->Salary Q3: This relation is 3NF BranchNo ---->city, location, phone

BillDetails Q1: This relation is 1NF Because no repeating groups, No multivalued attribute, No composite attributes, No nested relations Q2: This relation is 2NF Because no partial dependencies BillNumber ---> Price, Quantity CategoryName Q3: This relation is 3NF