ALL SOFTWARE EXERCISES
- EXERCISES HOME PAGE (750)
- Access 2010 (66)
- Access VBA Macros (17)
- Advanced VBA (29)
- ASP.NET MVC (0)
- ASP.NET webforms - C# (25)
- ASP.NET webforms - VB (27)
- Excel 2010 (83)
- Excel 2013 (10)
- Excel VBA Macros (37)
- Power BI - Excel 2013 (25)
- Power BI Desktop (0)
- PowerPivot 2010 (26)
- Report Builder 3.0 (42)
- SQL (115)
- SSAS - multidimensional (21)
- SSAS - tabular (29)
- SSIS Integration Services (18)
- SSRS Reporting Services (53)
- Visual Basic 2010 (42)
- Visual C Sharp 2010 (65)
- WPF - Visual C# (20)
- Creating databases - overview (2)
- Simple Queries (5)
- Setting criteria using WHERE (4)
- Outputting to Excel (1)
- Calculations (4)
- Calculations using dates (3)
- Basic joins (6)
- More exotic joins (3)
- Aggregation and grouping (6)
- More complicated grouping (1)
- Views (6)
- Subqueries (2)
- Overview of functions (4)
- Overview of stored procedures (3)
- Detailed stored procedures (4)
- Variables (8)
- Parameters and return values (8)
- Testing conditions (1)
- Looping (1)
- Scalar functions (6)
- Transactions (4)
- Creating tables (3)
- Temporary tables and table variables (10)
- Table-valued functions (6)
- Derived tables and CTEs (7)
- Cursors (3)
- Error-handling (2)
- Dynamic SQL (2)
Exercise: Populate a column, then (maybe) roll back the transaction
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.
The answer to the exercise will be included and explained if you attend the Wise Owl course listed below!
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.
Type in and run the following script to generate a new column called NumberEnemies in the tblEpisode table:
ALTER TABLE tblEpisode
ADD NumberEnemies int
Write an update query which will set this column to equal the number of enemies for each episode (but within a transaction), then:
- Roll back this transaction if more than 100 rows are affected (displaying a suitable message, as shown overleaf); or
- Commit it otherwise and show a list of all of the episodes, including the newly populated field.
Use @@RowCount to see how many rows are affected, but don't forget to store this in a variable immediately after running the update so that its value doesn't get overwritten.
Note that the syntax of the update query is nasty:
-- set the number of enemies for each episode
NumberEnemies = (
tblEpisodeEnemy AS ee
ee.EpisodeId = e.EpisodeId
tblEpisode AS e
When you run this query, you should see something like this:
Because 117 rows were updated, your query should roll back the transaction.
Now change the threshold in the query from 100 to 120 and re-run it. This time the query should update the column, and display the results:
You have to wait until episode id 15 to get more than one enemy (at which point 3 come along at once).
When you've got this working, optionally save your query as Counting your enemies.sql, then close it down.