Technical Interview Questions and Answers :: Syntel Inc.
- Select All
- Oracle PLSQL
- Java
- C++
- WebMethod
- C
- DBMS
- Operating System
- Oracle Apps HRMS
- Networking
- Soft. Engineering
- HR Question in TR
- Data Structure
- .NET
- SQL
71 / 161
There are several advantages of normalization as under:
* Faster sorting and index creation.
* A larger number of clustered indexes.
* Narrower and more compact indexes.
* Fewer indexes per table, which improves the performance of INSERT, UPDATE, and DELETE statements
* Fewer null values and less opportunity for inconsistency, which increase database compactness.
Beside the above benefits there are few disadvantages as well:
* Increased amount of Normalization increases the amount of complexity of joins between tables and that hinders the performance.
72 / 161
It guarantees that the spurious tuple generation does not occur with respect to relation schemas after decomposition.
73 / 161
The domain of an attribute must include only atomic (simple, indivisible) values.
74 / 161
It is based on the concept of full functional dependency. A functional dependency X -> Y is full functional dependency if removal of any attribute A from X means that the dependency does not hold any more.
75 / 161
A relation schema R is in 2NF if it is in 1NF and every non-prime attribute A in R is fully functionally dependent on primary key.
76 / 161
A relation schema R is in 3NF if it is in 2NF and for every FD X -> A either of the following is true
> X is a Super-key of R.
> A is a prime attribute of R.
In other words, if every non prime attribute is non-transitively dependent on primary key.
77 / 161
A relation schema R is in BCNF if it is in 3NF and satisfies an additional constraint that for every FD X -> A, X must be a candidate key.
78 / 161
A relation schema R is said to be in 4NF if for every Multivalued dependency X ->-> Y that holds over R, one of following is true
> X is subset or equal to (or) XY = R.
> X is a super key.
79 / 161
A Relation schema R is said to be 5NF if for every join dependency {R1, R2, ..., Rn} that holds R, one the following is true
> Ri = R for some i.
> The join dependency is implied by the set of FD, over R in which the left side is key of R.
80 / 161
A relation is said to be in DKNF if all constraints and dependencies that should hold on the constraint can be enforced by simply enforcing the domain constraint and key constraint on the relation.