Jyorianne Daniel Thursday, April 01, 2011

1. Normalization is the process of designing a data model to efficiently store data in a database. The end result is that redundant data is eliminated, and only data related to the attribute is stored within the table. To avoid redundancy and to constructing an efficient database we use normalization. It is basically a concept which is used to construct efficient database

2.

The Most Profound benefits of normalization on a database are: Reduction of redundant data A better handle on database security Greater overall database organization Data consistency within the database A much more flexible database design Tables are smaller and more efficient

3. The normalization process involves a few steps and each step is called a form. Forms range from the first normal form (1NF) to fifth normal form (5NF). There is also higher level, called domain key normal form (DK/NF),and Boyce-Codd Normal Form (BCNF).

4. Functional dependencies in normalization is important because without having a functional relationship between attributes Information may be stored redundantly wasting storage ,also problems with update anomalies :Insertion anomalies, Deletion anomalies, Modification anomalies. And the mixing attributes of multiple entities may cause problems

5. A Functional Dependency describes a relationship between attributes in a single relation. An attribute is functionally dependant on another if we can use the value of one attribute to determine the value of another.

Jyorianne Daniel Thursday, April 01, 2011

6. Given the relation R(A,B,C) prove A C, when A B and B C This proves that C is functionally dependence on A, so the value of A determines the value of C When {(AB), (BC)} , then {(AB), (BC), (AC), (ABC)}, and {(ABC)};

7. The improper identification and handling of business rules can affect the design of a database in many ways. Without proper identification of what are the business rules or clear business rules data can be entered incorrectly or entered in wrong tables or fields, making records incorrect, and hence making the database inaccurate. A business rule defines or constrains one aspect of your business that is intended to assert database structure or influence the behavior of your database.If business rules are corrupted the design may not reflect what the designer may want to portray

8. Armstrongs Axioms
Axiom of reflexivity If , then Axiom of augmentation If , then Axiom of transitivity If and , then for any Z

Jyorianne Daniel Thursday, April 01, 2011

9. Functional dependency plays a key role in establishing and maintaining a relationship among the datas that are functionally related to one another and they are separated from other non-related datas thus providing clear relationship among the set of datas present. Database integrity is concerned with the accuracy, correctness, and validity of data in a database. It involves ensuring that the data manipulation operations done on the database by authorized database users are correct, and that they do not change the consistency and validity of data. A functional dependency constraint specifies a functional dependency of an attribute set on another attribute set in a relation. Functional dependency can be used to implement integrity constraints by ensuring that related data are inserted and handled correct (update and deletion).

10. Referential integrity is a database constraint that ensures that references between data are indeed valid and intact. Referential integrity is a fundamental principle of database theory and arises from the notion that a database should not only store data, but should actively seek to ensure its quality. Integrity constraints are used to ensure accuracy and consistency of data in a relational database. Data integrity is handled in a relational database through the concept of referential integrity. There are many types of integrity constraints that play a role in referential integrity. An integrity constraint that is enforced by the DBMS is an implicit integrity constraint. Otherwise, it is an explicit integrity constraint.

Implicit integrity constraints constitute the basis for the prevention method. Explicit integrity constraints are used in the detection method. a) The prevention method ascertains that an impending database modification (insertion, deletion, or update) does not produce an incorrect database state before it is allowed to proceed, and prevents the execution of any modification that would violate the database consistency.

Jyorianne Daniel Thursday, April 01, 2011

b) The detection method, on the other hand, allows modifications to take place, and subsequently verifies the consistency of the new database state, detecting incorrect data and the modification that causes inconsistency, if any.