Roy
2012-10-20 08:29:19 UTC
2. Normalization is the process of finding common data in the database. True/False
3. Not being able to insert data because other data is required is an example of an insertion anomaly. True/False
4. An insertion anomaly occurs when you enter data inaccurately. True/False
5. An update anomaly occurs when you have to update the same data in multiple places. True/False
6. An update anomaly occurs when you have date fields conflict in the database. True/False
7. A deletion anomaly occurs when deleting a set of data accidentally deletes other unintended data. True/False
8. A deletion anomaly occurs when you are unable to delete data in a primary key table because a foreign key table contains records related to that data. True/False
9. Normal forms are sets of rules designed to remove anomalies and redundancy from database design. True/False
10. Normal forms are the forms programmers create to access database data more easily. True/False
11. The first normal form removes all repeating groups and arrays. True/False
12. When all entities are in the first normal form, a database is ready to use. True/False
13. Rather than put several values in a single column, you should create several columns and number them like column1, column2 , etc. True/False
14. Second normal form removes functional dependencies. True/False
15. Second normal form combines several sub themes into one entity. True/False
16. Functional dependencies consist of groups of related attributes that form subsets within an entity. True/False
17. Functional dependency refers to one entity depending on another entity for it meaning. True/False
18. Failure to normalize a database can lead to numerous problems. True/False
19. Failure to normalize a database never causes problems. True/False
20. Third normal form removes transient dependencies. True/False
21. A transient dependency is where an attribute depends on another attribute for its meaning and not on the key. True/False
22. A transient dependency is one that comes and goes. True/False
23. If you have two related entities, one named Customer and on CustomerOrder, you should always add the customer’s name to both entities because you know you will want to see the name with the order when you look at the data. True/False
24. You should always have others review your entity relation diagrams. True/False
25. You should never have others review your entity relation diagrams. True/False