EXERCISE TOPIC▼
SQL EXERCISES▼
SQL EXERCISES▼
- Simple Queries (4)
- Setting criteria using WHERE (5)
- Calculations (7)
- Calculations using dates (4)
- Basic joins (8)
- More exotic joins (2)
- Aggregation and grouping (8)
- Views (5)
- Subqueries (5)
- Stored procedures (5)
- Variables (8)
- Parameters and return values (11)
- Testing conditions (1)
- Looping (3)
- Scalar functions (6)
- Transactions (5)
- Creating tables (5)
- Temporary tables and table variables (9)
- Table-valued functions (6)
- Derived tables and CTEs (13)
- Dynamic SQL (4)
- Pivots (2)
- Triggers (2)
- Archived (70)
SQL | Archived exercise | Designing a DVD library database
This exercise is provided to allow potential course delegates to choose the correct Wise Owl Microsoft training course, and may not be reproduced in whole or in part in any format without the prior written consent of Wise Owl.
You can learn how to do this exercise on the relevant Wise Owl classroom training course (sadly for the moment only in the UK).
Software ==> | SQL (198 exercises) |
Version ==> | Any version of SQL Server |
Topic ==> | Archived (70 exercises) |
Level ==> | Harder than average |
You need a minimum screen resolution of about 700 pixels width to see our exercises. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.
Your friend Oscar has contacted you. He is opening a DVD library, and wants to computerise his stock and lending records. He has asked you to design a database for him.
On paper, design a database for Oscar - using these thoughts to help you:
- Each member can rent out more than one DVD on each occasion, and can also spend money on other goods (such as sweets or popcorn). However, you only need to keep track of which DVDs are in stock.
- The DVD store will typically buy many different copies of the same film, each of which needs to be tracked separately.
If you have time you could try putting your database into practice in SQL Server - or have a look at one possible answer, as shown below.