- 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 | Transactions exercise | Using Insert, Update and Delete in transacitons
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.
First store the value of Westeros in a variable. Now write an insert statement to add the value of this variable into the ContinentName field:
INSERT INTO tblContinent (ContinentID,ContinentName)
Note that to do this you will first need to get SQL Server to overwrite the ContinentId identity column by running the command SET IDENTITY_INSERT tblContinent ON. Don't forget to turn this property off at the end of your query.
After running the Insert statement, comment it out but leave the variable.
You should now see Westeros appearing in the list of continent names when you select them. The question is: which is the deadliest continent?
Start a TRANSACTION to delete the continent held in the variable, using this syntax:
WHERE ContinentName = @Continent
If the first letter of your name is not equal to (<>) the first letter of the variable (W) then roll back the transaction:
In this case, show the message You have died and update the continent name of Westeros to Seven Kingdoms, then select all the continents.
Set the ELSE condition to show You have won and to then select all the continents.
The outcome now will depend on your name. If it is W then you will see no continent:
You survived and the seven kingdoms of Westeros are gone. Danny would be proud!
For those less fortunate of us, you will have died. Change the <> to an = and rerun the script. This time you should see Seven Kingdoms and a happier message.
Optionally save this as Game Of Thrones.sql and close it down.