- Access exercises (91)
- C# exercises (79)
- Excel exercises (278)
- Power Apps exercises (13)
- Power Automate exercises (18)
- Power BI exercises (139)
- Power Platform exercises ()
- Python exercises (28)
- Report Builder exercises (141)
- SQL exercises (198)
- SSAS exercises (51)
- SSIS exercises (46)
- SSRS exercises (99)
- VBA exercises (85)
- Visual Basic exercises (46)
- 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 | Triggers exercise | Create a trigger to stop people deleting UK events
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.
- 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.
The aim of this exercise it to stop anyone deleting events which happened in the UK (country number 7). To do this create a trigger which operates on the tblEvent table.
Use INSTEAD OF UPDATE rather than AFTER UPDATE, so that the deletion won't occur unless you specifically authorise it.
In your trigger, create and set the value of the following two variables from the deleted table:
|Variable||What it should contain|
|@EventId||The number of the event someone is trying to delete|
|@CountryId||The country number in which this event took place.|
If this event didn't take place in country id number 7, delete it:
-- if country is not UK (7), allow deletion
IF @CountryId <> 7
WHERE EventId = @EventId
Test that your query works by deleting events which did and didn't happen in the UK.
Be careful! When doing this manually by editing rows, the number of rows reported can be wrong. You may need to close your table and then re-open it to check that UK events haven't been deleted.
Optionally, save this query as Brexit events.sql, then close it down.