WISE OWL EXERCISES
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 (3)
- Stored procedures (5)
- Variables (8)
- Parameters and return values (11)
- Testing conditions (1)
- Looping (3)
- Scalar functions (6)
- Transactions (4)
- Creating tables (4)
- Temporary tables and table variables (9)
- Table-valued functions (6)
- Derived tables and CTEs (11)
- Dynamic SQL (4)
- Pivots (2)
- Triggers (2)
- Archived (70)
SQL | Creating tables exercise | Create and populate table of genres using SQL
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.
The answer to the exercise will be included and explained if you attend the course listed below!
| Software ==> | SQL (192 exercises) |
| Version ==> | Any version of SQL Server |
| Topic ==> | Creating tables (4 exercises) |
| Level ==> | Average difficulty |
| Course ==> | Advanced SQL |
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.
If you haven't already done so, run the stored procedure in the above folder to generate a database of books and authors.
Create a query or stored procedure to create the following table of book genres called tblGenre (the rating is a number between 1 and 10 you can assign to each genre):
The table should have 3 columns - you get bonus points for indexing the GenreName column
Now add code to insert records into this table then display them - here's a suggestion for what to add:
If you don't like science fiction, your ratings will be different
Run your query to check it works - you should see something like this:
Here we've also used @@IDENTITY to show the id number of the last row added
Now run your query again - it should now fall over, because the tblGenre table already exists.
Add a statement at the start of your query to drop the tblGenre table if it exists, and run the query again - it should now work.
Optionally, save your query as Generate genres.sql, then close it down.