Thanks.

© All Rights Reserved

15 views

Thanks.

© All Rights Reserved

- Balthazar's Marvelous Afternoon
- WEEK 3 - Database Management Systems
- Database Design
- Normalization A
- Dbms Joins
- Windows 2003 Terminal Services
- MS-SQL
- Chapter 9 ER Diagrams + 10 Normalization
- DBMS
- Chapter 09
- GTU Exam Paper
- Book Chapter - Vaisman and Zimányi, 2014 - Database Concepts
- Elements of Short Story
- Dbms SQL Overview
- Parts Compatibility Table
- HPUFTLAB1
- Castor Reference Guide 1
- C++ for Game Programmers
- GeoNetworkUserManual
- InteliLIGHT LoRa - Szada Case Study

You are on page 1of 5

DBMS Normalization

DBMS NORMALIZATION

http://www.tutorialspoint.com /dbm s/database_norm alization.htm

Functional Dependency

Functional dependency (FD) is set of constraints between two attributes in a relation. Functional

dependency says that if two tuples have same values for attributes A1, A2,..., An then those two tuples

must have to have same values for attributes B1, B2, ..., Bn.

Functional dependency is represented by arrow sign (), that is XY, where X functionally determines

Y. The left hand side attributes determines the values of attributes at right hand side.

Armstrong's Axioms

If F is set of functional dependencies then the closure of F, denoted as F+ , is the set of all functional

dependencies logically implied by F. Armstrong's Axioms are set of rules, when applied repeatedly

generates closure of functional dependencies.

Reflexive rule: If alpha is a set of attributes and beta is_subset_of alpha, then alpha holds beta.

Augmentation rule: if a b holds and y is attribute set, then ay by also holds. That is adding

attributes in dependencies, does not change the basic dependencies.

T ransitivity rule: Same as transitive rule in algebra, if a b holds and b c holds then a c

also hold. a b is called as a functionally determines b.

T rivial: If an FD X Y holds where Y subset of X, then it is called a trivial FD. Trivial FDs are

always hold.

Non-trivial: If an FD X Y holds where Y is not subset of X, then it is called non-trivial FD.

Completely non-trivial: If an FD X Y holds where x intersect Y = , is said to be completely

non-trivial FD.

Normalization

If a database design is not perfect it may contain anomalies, which are like a bad dream for database itself.

Managing a database with anomalies is next to impossible.

Update anomalies: if data items are scattered and are not linked to each other properly, then

there may be instances when we try to update one data item that has copies of it scattered at several

places, few instances of it get updated properly while few are left with there old values. This leaves

database in an inconsistent state.

Deletion anomalies: we tried to delete a record, but parts of it left undeleted because of

http://www.tutorialspoint.com/cgi-bin/printpage.cgi

1/5

8/5/2014

DBMS Normalization

Insert anomalies: we tried to insert data in a record that does not exist at all.

Normalization is a method to remove all these anomalies and bring database to consistent state and free

from any kinds of anomalies.

This is defined in the definition of relations (tables) itself. This rule defines that all the attributes in a

relation must have atomic domains. Values in atomic domain are indivisible units.

We re-arrange the relation (table) as below, to convert it to First Normal Form

Each attribute must contain only single value from its pre-defined domain.

Before we learn about second normal form, we need to understand the following:

Prime attribute: an attribute, which is part of prime-key, is prime attribute.

Non-prime attribute: an attribute, which is not a part of prime-key, is said to be a non-prime

attribute.

http://www.tutorialspoint.com/cgi-bin/printpage.cgi

2/5

8/5/2014

DBMS Normalization

Second normal form says, that every non-prime attribute should be fully functionally dependent on prime

key attribute. That is, if X A holds, then there should not be any proper subset Y of X, for that Y A

also holds.

We see here in Student_Project relation that the prime key attributes are Stu_ID and Proj_ID. According

to the rule, non-key attributes, i.e. Stu_Name and Proj_Name must be dependent upon both and not on

any of the prime key attribute individually. But we find that Stu_Name can be identified by Stu_ID and

Proj_Name can be identified by Proj_ID independently. This is called partial dependency, which is not

allowed in Second Normal Form.

We broke the relation in two as depicted in the above picture. So there exists no partial dependency.

For a relation to be in Third Normal Form, it must be in Second Normal form and the following must

satisfy:

No non-prime attribute is transitively dependent on prime key attribute

For any non-trivial functional dependency, X A, then either

http://www.tutorialspoint.com/cgi-bin/printpage.cgi

3/5

8/5/2014

DBMS Normalization

X is a superkey or,

A is prime attribute.

We find that in above depicted Student_detail relation, Stu_ID is key and only prime key attribute. We

find that City can be identified by Stu_ID as well as Zip itself. Neither Zip is a superkey nor City is a prime

attribute. Additionally, Stu_ID Zip City, so there exists transitive dependency.

We broke the relation as above depicted two relations to bring it into 3NF.

BCNF is an extension of Third Normal Form in strict way. BCNF states that

For any non-trivial functional dependency, X A, then X must be a super-key.

In the above depicted picture, Stu_ID is super-key in Student_Detail relation and Zip is super-key in

ZipCodes relation. So,

Stu_ID Stu_Name, Zip

And

http://www.tutorialspoint.com/cgi-bin/printpage.cgi

4/5

8/5/2014

DBMS Normalization

Zip City

Confirms, that both relations are in BCNF.

http://www.tutorialspoint.com/cgi-bin/printpage.cgi

5/5

- WEEK 3 - Database Management SystemsUploaded byAngelique Garrido V
- Database DesignUploaded bypiyush_ji
- Normalization AUploaded bymanishbafna4u
- MS-SQLUploaded bymanu424
- Chapter 9 ER Diagrams + 10 NormalizationUploaded byMartinLuk
- DBMSUploaded byAnonymous FGU9srT6j
- Chapter 09Uploaded byAnn Lorraine Mamales
- GTU Exam PaperUploaded byAbc
- Book Chapter - Vaisman and Zimányi, 2014 - Database ConceptsUploaded byBenard Mapako

- Balthazar's Marvelous AfternoonUploaded byWendy Marie
- Elements of Short StoryUploaded byWendy Marie
- Dbms SQL OverviewUploaded byWendy Marie
- Dbms JoinsUploaded byWendy Marie
- Windows 2003 Terminal ServicesUploaded byWendy Marie
- Parts Compatibility TableUploaded byWendy Marie
- HPUFTLAB1Uploaded byLou T. Jacob

- Castor Reference Guide 1Uploaded byjrtelemaco7024
- C++ for Game ProgrammersUploaded bydharmasaputra
- GeoNetworkUserManualUploaded byregsux
- InteliLIGHT LoRa - Szada Case StudyUploaded byrajdeep_kacha
- Python Ch 01 lecture notesUploaded bydweebo
- Modern Work Instructions JLX3DUploaded byMarceloGonçalves
- Camera User ManualUploaded byWade Woody Woodpecker
- Dsd 4 Win TutorialUploaded bygus289
- MODULES PhisingUploaded bysivagami
- Paging and Access Grant ControlUploaded bymustaq12
- GGTRONICS SSDAC-3DPISUploaded bykrispr4u
- A New Integrated Robot Vision SystemUploaded byHieu Tran
- S11003QUO01r0Uploaded byFARHAN
- Autocad - Using Batch File, Script and List TogetherUploaded bylarouc07
- !!! ApplicationHelp ERPTM IntegrationUploaded byLaura Sonea
- Nokia Ran Kpis Part 1 RrcUploaded byMonchai Thailand
- Samsungs TechnologyUploaded bylokeshlok
- CCTV Product Catalogue 2009Uploaded byaran1000
- Oracle Applications Technical Erp r11i, r12_ Attachments API - Fnd_documents_pkg, Fnd_attached_documents_pkgUploaded byDivakar Mani
- TestUploaded byeblwebadmin
- ELE107_ELE107-Week2-2014.pdfUploaded bypursey
- Intelligent Web ApplicationsUploaded byrajashekarpula
- Live Assistance.pdfUploaded byMohamed Zaki
- Release Notes (Learn 9.1 SP 7)Uploaded byGiovanna Spada
- EICT BrochureUploaded byprof_kt
- Sweet Home 3D User GuideUploaded byessmerrtwety
- Credit Memo Workflow11Uploaded byfaca9883
- Mantık DevreleriUploaded bymustafakorkmz
- What is Immersive Multimedia8.1FUploaded byfathihanirif
- Dlink 5222l ManualUploaded byghenriquez