- 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 | Scalar functions exercise | Create various functions to show information about episodes
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 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.
First (if you haven't already done so) run the script shown above to generate the Doctor Who training database.
See how many of the following functions you can create in the time left to you!
-- show all these functions working
-- function to count number of companions for a given episode
dbo.fnNumberCompanions(EpisodeId) AS Companions,
-- function to count the number of enemies for an episode
dbo.fnNumberEnemies(EpisodeId) AS Enemies,
-- function to count the number of words (hint: use a combination
-- of LTRIM and RTRIM to remove leading and trailing spaces, then
-- REPLACE to change all spaces to empty strings and compare the
-- LEN of the string before and after this change!)
dbo.fnWords(Title) AS Words
Here's what you should see when you run the query, if you manage to create all of the functions listed:
Four episodes have 7 words each.
When (if?) you finish, optionally save your query as Too many functions.sql, then close it down.