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 | Temporary tables and table variables exercise | Get a temporary table to hold stored procedures and functions
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!
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.
Run the following command in SQL:
-- show tables, views, etc in your database
SELECT * from sys.objects
This should list out all of the tables, views, functions, stored procedures, etc in your database. We're interested in the following two codes:
|Code||What it is|
Your manager (probably the same annoying one who has cropped up in previous exercises for SQL) has asked you to create a single table listing out the name, object type and date created for:
- All of the non-system stored procedures (apart from those which contain the word Episodes); as well as
- All of the non-system scalar functions.
Use a temporary table or table variable to accumulate this information. Here's what you should see when you show the rows in this table:
You may have fewer or more objects, depending on which exercises you've done, and your creation dates will certainly be different.
When you've got this all working, show your trainer (s/he'll be impressed), then optionally save this query as System objects.sql and close it down.