- 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 a scalar function to determine type of each episode
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.
The aim of this exercise is to create a function called fnEpisodeDescription such that you can count how many episodes there are of each type:
-- count number of episodes of each type
dbo.fnEpisodeDescription(Title) AS 'Episode type',
COUNT(*) AS 'Number of episodes'
Here's what this should return:
It's reassuring to see that the number of first and second parts are the same!
To write this function use the CHARINDEX function to determine whether one string of text exists within another:
Your function should look for the word Part 1 (or failing that, Part 2) in the title passed in.
As a guide, CHARINDEX('owl','Wise Owl') would return 6, whereas CHARINDEX('fox','Wise Owl') would return 0.
When you've got your function and query working, save (optionally) the SQL as Part of a couple.sql, then close it down.