Rent-A-Movie Database Design Guide
Rent-A-Movie Database Design Guide
To resolve many-to-many relationships, the project guide recommends avoiding them by ensuring that all tables have a primary key. This suggests using intermediary tables to separate entities where many-to-many relationships might naturally occur, effectively normalizing the data .
The project requires creating queries for a Customer List and a Transaction List. The Customer List should include ID, phone number, customer name, street address, city, state, zip code, and be sorted by customer's last name without duplicates. The Transaction List should include date, customer name, video name, price, tax, and total price, sorted by customer's last name and date .
The guidelines suggest enforcing referential integrity within the table relationships in the database. This involves creating appropriate table relationships and ensuring that primary and foreign keys are used correctly to maintain the integrity of the data .
The printouts must include all database elements such as tables, relationships, queries, and reports. They should be presented with a cover sheet with the student's name and ID, and all documentation should be neatly stapled together, without using folder covers .
The guidelines specify that movies rent for $3-$5 each, plus a 10% entertainment tax. This information should be used to calculate the total price for each movie rental in the database, including these details in reports and transactions .
The database should include features such as searching for customers by last name or phone number, entering a zip code to find the city and state, keeping track of rented movies along with dates and total spending, sending personalized letters addressing customers by their first name, and searching for movies by name, type, or actor. These features aim to improve the store's marketing and service offerings .
The database should include tables that allow for actor information to be associated with movies. This likely involves creating an intermediary table linking actors and movies to facilitate searches by actor, considering that a movie can have multiple search-worthy actors .
Creating the schema involves determining the logical structure and relationships of the data, which is crucial as it sets the foundation for the rest of the database design. Without a correct schema, building a functional and efficient database aligned with project goals would be challenging .
Avoiding duplicate rows ensures that reports and data outputs are accurate and concise, reducing redundancy and improving data integrity. This is important for reliable analysis and decision-making, as well as for maintaining a streamlined database .
Transaction data should be organized by customer and date, including fields such as customer name, date, video name, and total price (including tax). Reports should group transactions by customer, then by date, and sort video name within each date. Additionally, the total amount spent by each customer on each date and overall should be displayed, ensuring it fits on 2-3 pages in portrait view .