1. Normalization works through a series of stages called normal forms.
2. Normalization produces a lower normal form.
3. Normalization is a process that is used for changing attributes to entities.
4. In order to meet performance requirements, you may have to denormalize portions of the database design.
5. Denormalization produces a lower normal form.
6. Normalization is a very important database design ingredient and the highest level is always the most desirable.
7. A table is in BCNF if every determinant in the table is a candidate key.
8. A table is in BCNF if every determinant in the table is a foreign key
9. A table is in fourth normal form if it is in third normal form and has no independent multivalued dependencies.
10. Relational models view the data as part of a table or collection of tables in which all key values must be identified.
11. Repeating groups must be eliminated by making sure that each row defines a single entity
12. Dependency diagrams are very helpful in getting a bird’s-eye view of all the relationships among a table’s attributes.
13. Dependencies that are based on only a part of a composite primary key are called transitive dependencies.
14. All relational tables satisfy the 1NF requirements.
15. With partial dependencies, data redundancies occur because every row entry requires duplication of data.
16. Converting a database format from 1NF to 2NF is a complex process.
17. Because a partial dependency can exist only if a table's primary key is composed of several attributes, if a table in 1NF has a single-attribute primary key, then the table is automatically in 2NF.
18. A table is in 2NF if it is in 1NF and it includes no partial dependencies.
19. It is possible for a table in 2NF to exhibit transitive dependency, where one or more nonprime attributes functionally determine other nonprime attributes.
20. A determinant is any attribute whose value determines other values within a column.
21. A dependency of one nonprime attribute on another nonprime attribute is a partial dependency.
22. Atomic attributes are attributes that can be further divided
23. Normalization should be part of the design process.
24. Normalization represents a micro view of the entities within the ERD.
25. The combination of normalization and ER modeling yields a useful ERD, whose entities may now be translated into appropriate relationship structures.
26. A good relational DBMS excels at managing denormalized relations.
27. The advantage of higher processing speed must be carefully weighed against the disadvantage of data anomalies.
28. Normalization purity is easy to sustain in the modern database environment.
29. Unnormalized database tables often lead to various data redundancy disasters in production databases.
30. Attributes should clearly define participation, connectivity, and document cardinality.
31. Repeating groups must be eliminated by making sure that each column defines a single entity
32. Dependencies can be identified with the help of the dependency diagram.
33. Data redundancies are caused by the fact that every row entry requires duplication of data
