In Chapter 9, you learned to write the proper sequence of activities when designing a database. In this final project you will:
Design a Video Rental Database (The initial ERD was shown in your textbook in figure 9.7. Chapter 9). The design must support all the rental activities, customer payment tracking, and employee work schedules, as well as track which employees checked out the videos to the customer.
1. Writing the design activity sequence (Chapter 9).
Figure 9.4 and Problem 1a (pg. 392) are examples of this.
2. CONCEPTUAL DESIGN
After you finish writing the design activity sequence (Chapter 9), complete the ERD in VISIO (Chapters 5, 6 & 9) to ensure that the database design can be successfully implemented. (Make sure the design is normalized properly and can support the required transactions.)
3. PHYSICAL DESIGN
Write the script in notepad that contains the SQL code to create your design (Chapter 7 & 9). Run the script in the database of your choice.
Submit in Blackboard
1. Design Activity Sequence in WORD or VISIO.
2. Final ERD in VISIO format
3. Table creation and insert statements in notepad script.
4. Saved copy of your results from Oracle or MS SQL.
I HAVE NO IDEA HOW TO DO THIS PROJECT. THE BOOK IS:
DATABSE FUNDAMENTALS (SEVENTH EDITION). I NEED HELP. CAN SOMEONE HELP ME AND TELL ME WHAT TO DO BECAUSE I DON’T GET IT. THIS PROJECT IS WASTING MY TIME, BECAUSE I DON’T UNDERSTAND "WHERE DO I START?"
Storm Sams says
First of all, good luck to you as you go through the process of becoming a web geek :). The book seems to be confusing you a bit because this all sounds to simple. Get some coffee, grab a sandwich, and then let things soak in.
1. Ok, let’s figure out each entity needed for each of the activities. For example, tbl_Customers will contain customers who will be doing the rentals, tbl_Videos are the videos to be rented, tbl_SalesRep will be the employee who did the rental sale, and etc You are going to be deriving entities who have relationships on one another (i.e., tbl_Videos would have a many-to-one relationship on tbl_Customers). If you come up with an entity but that entity have no relationship on another entity you come up with, throw it out. Follow the rules of normalization; this is huge and the basis for what your book is trying to get at so an understanding of the first, second, and third normal forms will help you out phenomely in this process.
2. I’m not sure on this one. I actually do my database designs using UML as C# or VB class diagrams representing my data access layer. What is your book saying? However your book is explaining it, conceptual design should make sense to you after completing #1.
3. The easy part. Based on your RDBMS, write a script that will create your database and your objects (tables, views, and stored procedures). Write seperate scripts to enable constraints, disable constraints, and delete all objects if necessary.