1. A database contains one or more related tables. Each table holds all of the information
2. An _______ is a person, place, thing or concept about which data can be collected. Examples include EMPLOYEE, HOUSE, CAR
3. Entities will be made up of __________ that represent that entity. An example of _________ for the entity 'Customer' would be ID, First Name etc.
4. Taking the example of an online subscription site (to purchase e-books), possible entities could be:
5. Links between entities are also called:
6. There are different types of relationships including: one to one, one to many and ______________________
7. Assuming a world in which a husband can only have one wife (and vice versa), this would be an example of a:
8. An example of a one to many relationship could be Father to children. A child can have only one father. A father can have many children.
9. A many to many relationship is an excellent idea when designing tables, because it allows for greater flexibility.
10. It is much preferred to find a way to change a many to many relationship to a many to one or one to many relationship instead.
11. What type of relationship is being modelled in this example?
12. To solve the 'many to many' problem with Customers and E-books, which of the following solutions could be used?
13. When designing relationships it is helpful to remember that: the 'many' side is usually the ______ key. The 'one' side is usually the primary key.
14. Before setting up a database, working out the entity relationships, attributes and entities themselves is called:
15. Almost always, a Many-to-Many relationship conceals a _____________. For this reason, identifying and adding the _________________ to the model eliminates Many-to-Many relationships
16. Read the following excerpt that describes a particular scenario. How would you solve the problem?
17. What is the join/link table in this example and which of the following answers best describes its purpose?
18. It is usually (but not always) the case that the following is true:
19. The process of working out the entities, attributes and the entity relationships is called: attribute modelling
20. ER diagrams are used to analyze existing databases to find and resolve problems in logic or deployment. Drawing the diagram should reveal where it’s going wrong.