WISE OWL 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 | Testing conditions exercise | Changing stored procedure outcomes using IF
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 if you attend the course listed below!
- Go into SQL Server Management Studio;
- Open the SQL file you've just unzipped (you can press CTRL + O to do this); then
- Execute this script.
This will generate the database that you'll need to use in order to do this exercise (note that the database and script are only to be used for exercises published on this website, and may not be reused or distributed in any form without the prior written permission 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.
Using IF create a stored procedure that returns different results depending on the word passed in. You should be able to run:
--Try the stored procedure with each of the possible outcomes.
exec uspInformation 'Event'
exec uspInformation 'Country'
exec uspInformation 'Continent'
Here are the results you should see for the three commands above:
The top two results from running the stored procedure with each parameter value.
When you have this working try putting a different (made-up) word in to see what happens - you should get this:
The procedure will run, but none of the conditions are satisfied, so nothing happens!
Add a section of code which gives a message if a wrong word is put in.
The response should have a suitably annoying header.
To stop this appearing for the correct words try adding either a RETURN statement in each IF block, a separate IF using the NOT IN command or some ELSE clauses.
Optionally save this as Running Out Of Options.sql, then close it down.