Single valued normalisation, Database Management System

Single Valued Normalisation

 Codd in the year 1972 formed three normal forms (1NF, 2NF, and 3NF). These were based on functional dependencies between the attributes of a relation. Later Codd and Boyce proposed another normal form known as the Boyce-Codd normal form (BCNF). The fourth and fifth normal forms are based on multivalue and join dependencies and were proposed soon.  In this part we will do normal forms till BCNF only. Fourth and fifth normal forms are afar the scope of this course. For all practical purposes, BCNF or the3NF are quite adequate since they remove the anomalies talk about for most common situations. It should be obviously understood that there is no obligation to normalise relations to the maximum possible level. Performance should be engaged into account and sometimes an organisation may take a decision not to normalise, say, beyond third normal form. But, it should be noted that such designs should be careful sufficient to take care of anomalies that would result as of the decision above.

Intuitively, the second and third normal forms are planned to result in relations such that each relation have information about only one thing (either an relationship or a entity). A sound E-R model of the database would make sure that all relations either give facts about an entity or about a relationship resulting in the relations that are get being in 2NF or 3NF.

Normalisation results in decomposition of the original relation. It should be noted that decomposition of relation has to be always rely on principles, such as functional dependence, that ensure that the original relation may be reconstructed from the decomposed relations if and when needed. Careless decomposition of a relation can result in loss of information. We will talk about this in detail in the later section. Let us now describe these normal forms in more detail.

 

Posted Date: 3/7/2013 1:54:39 AM | Location : United States







Related Discussions:- Single valued normalisation, Assignment Help, Ask Question on Single valued normalisation, Get Answer, Expert's Help, Single valued normalisation Discussions

Write discussion on Single valued normalisation
Your posts are moderated
Related Questions
Project: Microsoft Access You have been asked by the ABC Tanning Salon to create a database that can be used to track the salon's customers.  You are to create a table in Access

Explain the conventions for displaying an ER schema as an ER diagram? An E-R Diagram scheme might describe certain constraints to that the contents of a database must conform.

Discuss the problem of Spurious tuples and how we may prevent it.    Ans:  A spurious tuple is, mainly, a record in a database that gets created while two tables are joined bad

Define weak and strong entity sets?  Weak entity  set:  entity  set  that  do not  have  key  attribute  of  their  own are  known as weak entity sets.  Strong entity set

Describe the static hash file with buckets and chaining and show how insertion, deletion and modification of a record can be performed. In static hash file organization, the wo

Question: Using the data model express the following queries in SQL. (a) Create the Table named "Cinema" and make the cinema_code to be the primary key of the relation and

Describe Specialsation and generalization? Specialisation /generalization: This is a top down and bottom up approach to the design of database. It displays the IS_A relation

Define single valued and multivalued attributes.  Single valued attributes: attributes with a single value for a particular entity are known as single valued attributes.   M

Differance between Unordered and ordered file ? Unordered file do no has any sequence although ordered file has arranged in a few sequence and data are assigned in ordered form

What is completeness constraint on generalization? Define the variation between total and partial design constraint. Give an example each.       Ans: Completeness Constraints