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 | Subqueries exercise | Using sub queries to filter with aggregates
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.
| Software ==> | SQL (198 exercises) |
| Version ==> | Any version of SQL Server |
| Topic ==> | Subqueries (5 exercises) |
| Level ==> | Relatively easy |
| Subject ==> | SQL training |
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.
Write a sub query to filter events to show only those which have an event name of longer than average length. You will need the AVG and LEN functions to do this.
The top 5 results out of 204 events.
You can run your subquery separately by highlighting it to show that the average EventName length is 26 characters:
The advantage of a sub query over typing 26 is that it will stay up to date if the average moves.
Optionally save this exercise as More words, more important.sql, and close it down.