Create a list of the tables in your database and determine the order in which the tables should be loaded. Remember the one side of a 1 to M or M to 1 relationship is always loaded first.
~ Based from the Cardinality spreadsheet and Relationships diagram, here is the Order of Data Load List:
| Order of Data Load | Table Name |
|---|---|
| 1 | Rating_Category_type_luv |
| 2 | Classification_type_luv |
| 3 | Varietal_type_luv |
| 4 | Address_type_luv |
| 5 | Phone_type_luv |
| 6 | Email_type_luv |
| 7 | Rating Category |
| 8 | Wine |
| 9 | Classification |
| 10 | Varietal |
| 11 | Wine_Varietal |
| 12 | Winery |
| 13 | Region |
| 14 | Website |
| 15 | Address |
| 16 | Winery_Address |
| 17 | Phone |
| 18 | Winery_Phone |
| 19 | |
| 20 | Winery_Email |
Enter data into two tables of your database. You only have to enter two rows of data in each table.
Use a select all statement to display the data that you entered into the two tables.
1. SELECT *
FROM Wine;
~ [Screen capture]
2. SELECT *
FROM Varietal_type_luv;
~ [Screen capture]
~ Or download the zipped database (60kb) in MS Access
1. Before this class how many databases did you design?
~ None. This Wine Stash/Collection Database is my first database design project.
2. What do you think of the outcome of your database that you designed in this class?
~ My Wine Collection Database is a good start, but still needs a lot of improvement and guidance. My client (my DH) will be very pleased with it :-) .
3. What did you learn new from this class that you did not already know about database design?
~ Everything I know regarding database design came from this class.
4. What did you like about the class?
~ That I learned how to design a database from this class. That you were prompt in grading and answering student's posted work and questions.
5. What would you change about the class?
~ Since this is my first database design learning and experience, I wish:
— That there be a reference material/textbook to support/reinforce lectures. Or at a minimum provide more step by step examples on how to do things on all lectures.
— That lectures be geared for and written with a beginner in mind since this class is an Introduction class (and would probably lessen questions and clarifications and would save us time grasping concepts).
— That clear explanations be given regarding Access and reference to Access Help only as reinforcement (Example: how to edit relationship type in edit relationships dialog box which I haven't found the answer to this yet).
— That assignments be worded clearly if screenshots, .mdb files should be posted. Example, database file on 2nd assignment for week 3 which can be interpreted as an exercise only, which will affect thoroughness/completeness (or lack of it) in assignment. I had a "to-post-or-not-to-post" attitude before posting them. To post is always better.
— That there be a Database Design Level II class to continue what we learned from this class.