Updated metadata

GraemeMalcolm · GraemeMalcolm · commit f894b0d70da3 · 2026-03-19T10:26:23.000-07:00
diff --git a/Instructions/Labs/01-get-started-with-tsql.md b/Instructions/Labs/01-get-started-with-tsql.md
@@ -3,7 +3,7 @@ lab:
   title: Get Started with Transact-SQL
   module: 'Module 1: Getting Started with Transact-SQL'
   description: In this exercise, you will use some basic SELECT queries to retrieve data from the AdventureWorks database.
-  duration: 124 minutes
+  duration: 30
   level: 100
   islab: true
 ---
diff --git a/Instructions/Labs/02-filter-sort.md b/Instructions/Labs/02-filter-sort.md
@@ -3,7 +3,7 @@ lab:
   title: Sort and Filter Query Results
   module: 'Module 2: Sorting and Filtering Query Results'
   description: In this exercise, you'll use the Transact-SQL SELECT statement to query and filter data in the AdventureWorks database.
-  duration: 148 minutes
+  duration: 30
   level: 100
   islab: true
 ---
@@ -150,14 +150,14 @@ Often, multiple rows in a table may contain the same values for a given subset o
 
 7. Run the modified query and note that the results include one row for each unique **Color** value. This ability to remove duplicates from the results can often be useful - for example to retrieve values in order to populate a drop-down list of color options in a user interface.
 
-9. Modify the query to add the **Size** field as shown here:
+8. Modify the query to add the **Size** field as shown here:
 
     ```sql
     SELECT DISTINCT Color, Size
     FROM SalesLT.Product;
     ```
 
-8. Run the modified query and note that it returns each unique combination of color and size.
+9. Run the modified query and note that it returns each unique combination of color and size.
 
 ## Filter results with the WHERE clause
 
@@ -301,7 +301,7 @@ This section contains suggested solutions for the challenge queries.
     FROM SalesLT.Address
     ORDER BY City
     ```
- 
+
 2. Retrieve the heaviest products:
 
     ```sql
diff --git a/Instructions/Labs/03a-joins.md b/Instructions/Labs/03a-joins.md
@@ -3,7 +3,7 @@ lab:
   title: Query Multiple Tables with Joins
   module: 'Module 3: Using Joins and Subqueries'
   description: In this exercise, you'll use the Transact-SQL SELECT statement to query multiple tables in the Adventureworks database.
-  duration: 98 minutes
+  duration: 30
   level: 100
   islab: true
 ---
@@ -214,7 +214,7 @@ This section contains suggested solutions for the challenge queries.
     JOIN SalesLT.SalesOrderHeader AS oh
         ON oh.CustomerID = c.CustomerID;
     ```
- 
+
 2. Retrieve customer orders with addresses:
 
     ```sql
diff --git a/Instructions/Labs/03b-subqueries.md b/Instructions/Labs/03b-subqueries.md
@@ -3,7 +3,7 @@ lab:
   title: Use Subqueries
   module: 'Module 3: Using Joins and Subqueries'
   description: In this exercise, you'll use subqueries to retrieve data from tables in the adventureworks database.
-  duration: 80 minutes
+  duration: 30
   level: 100
   islab: true
 ---
diff --git a/Instructions/Labs/04-built-in-functions.md b/Instructions/Labs/04-built-in-functions.md
@@ -3,7 +3,7 @@ lab:
   title: Use Built-in Functions
   module: 'Module 4: Using Built-in Functions'
   description: In this exercise, you'll use built-in functions to retrieve and aggregate data in the Adventureworks database.
-  duration: 114 minutes
+  duration: 30
   level: 100
   islab: true
 ---
diff --git a/Instructions/Labs/05-modify-data.md b/Instructions/Labs/05-modify-data.md
@@ -3,7 +3,7 @@ lab:
   title: Modify Data
   module: 'Module 5: Modifying Data'
   description: In this exercise, you'll insert, update, and delete data in the Adventureworks database.
-  duration: 134 minutes
+  duration: 30
   level: 100
   islab: true
 ---
diff --git a/Instructions/Labs/06-use-table-expressions.md b/Instructions/Labs/06-use-table-expressions.md
@@ -3,7 +3,7 @@ lab:
   title: Create queries with table expressions
   module: Additional exercises
   description: In this exercise, you'll use table expressions to query the Adventureworks database.
-  duration: 66 minutes
+  duration: 30
   level: 100
   islab: true
 ---
diff --git a/Instructions/Labs/07-combine-query-results.md b/Instructions/Labs/07-combine-query-results.md
@@ -3,7 +3,7 @@ lab:
   title: Combine query results with set operators
   module: Additional exercises
   description: In this lab, you will use set operators to retrieve results from the Adventureworks database.
-  duration: 56 minutes
+  duration: 30
   level: 100
   islab: true
 ---
diff --git a/Instructions/Labs/08-create-window-query-functions.md b/Instructions/Labs/08-create-window-query-functions.md
@@ -3,7 +3,7 @@ lab:
   title: Use window functions
   module: Additional exercises
   description: In this exercise, you'll apply window functions on the Adventureworks database.
-  duration: 36 minutes
+  duration: 30
   level: 100
   islab: true
 ---
diff --git a/Instructions/Labs/09-transform-data.md b/Instructions/Labs/09-transform-data.md
@@ -3,7 +3,7 @@ lab:
   title: Use pivoting and grouping sets
   module: Additional exercises
   description: In this exercise, you'll use pivoting and grouping sets to query the Adventureworks database.
-  duration: 50 minutes
+  duration: 30
   level: 100
   islab: true
 ---
diff --git a/Instructions/Labs/10-program-with-tsql.md b/Instructions/Labs/10-program-with-tsql.md
@@ -1,13 +1,13 @@
----
-lab:
-  title: Introduction to programming with Transact-SQL
-  module: Additional exercises
-  description: In this exercise, you'll use get an introduction to programming with Transact-SQL using the Adventureworks database.
-  duration: 80 minutes
-  level: 100
-  islab: true
----
-
+---
+lab:
+  title: Introduction to programming with Transact-SQL
+  module: Additional exercises
+  description: In this exercise, you'll use get an introduction to programming with Transact-SQL using the Adventureworks database.
+  duration: 30
+  level: 100
+  islab: true
+---
+
 # Introduction to programming with Transact-SQL
 
 In this exercise, you'll use get an introduction to programming with Transact-SQL using the **Adventureworks** database.
@@ -51,12 +51,12 @@ In this exercise, you'll use get an introduction to programming with Transact-SQ
 1. Run the code and review the output. This time, the PRINT statements result in the variable values being included in the messages produced by the code:
 
     ```
-    8:02:11 AM	Started executing on line 1
-    8:02:01 AM	Started executing query.
-    8:02:01 AM	680
-    8:02:01 AM	1431.50
-    8:02:01 AM	Finished executing query.
-    8:02:13 AM	SQL Server execution time: 00:00:00.010 | Total duration: 00:00:01.782
+    8:02:11 AM Started executing on line 1
+    8:02:01 AM Started executing query.
+    8:02:01 AM 680
+    8:02:01 AM 1431.50
+    8:02:01 AM Finished executing query.
+    8:02:13 AM SQL Server execution time: 00:00:00.010 | Total duration: 00:00:01.782
     ```
 
 1. Add a SELECT statement to output the variables as a resultset:
diff --git a/Instructions/Labs/11-create-stored-procedures.md b/Instructions/Labs/11-create-stored-procedures.md
@@ -1,13 +1,13 @@
----
-lab:
-  title: Create stored procedures and functions in Transact-SQL
-  module: Additional exercises
-  description: In this exercise, you'll create and run stored procedures in the Adventureworks database.
-  duration: 72 minutes
-  level: 100
-  islab: true
----
-
+---
+lab:
+  title: Create stored procedures and functions in Transact-SQL
+  module: Additional exercises
+  description: In this exercise, you'll create and run stored procedures in the Adventureworks database.
+  duration: 30
+  level: 100
+  islab: true
+---
+
 # Create stored procedures and functions in Transact-SQL
 
 In this exercise, you'll create and run stored procedures in the **Adventureworks** database.
@@ -29,7 +29,7 @@ Stored procedures are named groups of Transact-SQL statements that can be used a
     GROUP BY Name, ListPrice
     ORDER BY ListPrice DESC;
     ```
-    
+
 1. Run the code to create a stored procedure named **SalesLT.up_GetTopProducts**.
 1. In the query pane, type the following code under the CREATE PROCEDURE statement:
 
@@ -220,4 +220,3 @@ FROM SalesLT.ProductCategory AS c
 CROSS APPLY SalesLT.fn_SubCategories(c.ProductCategoryID) AS sc
 ORDER BY Category, SubCategory;
 ```
-
diff --git a/Instructions/Labs/12-implement-error-handling.md b/Instructions/Labs/12-implement-error-handling.md
@@ -1,13 +1,13 @@
----
-lab:
-  title: Implement error handling with Transact-SQL
-  module: Additional exercises
-  description: In this exercise, you'll use various Transact-SQL error handling techniques.
-  duration: 68 minutes
-  level: 100
-  islab: true
----
-
+---
+lab:
+  title: Implement error handling with Transact-SQL
+  module: Additional exercises
+  description: In this exercise, you'll use various Transact-SQL error handling techniques.
+  duration: 30
+  level: 100
+  islab: true
+---
+
 # Implement error handling with Transact-SQL
 
 In this exercise, you'll use various Transact-SQL error handling techniques.
@@ -16,7 +16,7 @@ In this exercise, you'll use various Transact-SQL error handling techniques.
 
 ## Observe unhandled error behavior in Transact-SQL
 
-The Adventureworks database contains details of products, including their size. Numeric values indicate the product size in centimeters, and you will use a stored procedure to convert these sizes to inches. 
+The Adventureworks database contains details of products, including their size. Numeric values indicate the product size in centimeters, and you will use a stored procedure to convert these sizes to inches.
 
 1. Open a query editor for your **Adventureworks** database, and create a new query.
 1. In the query pane, type the following code:
@@ -122,7 +122,7 @@ The message returned in the CATCH block indicates that an error occurred, but pr
 
 ## Throw the error to the client application
 
-So far, you've used a TRY/CATCH block to handle an error gracefully. The client application that calls the stored procedure does not encounter an exception. In multi-tier application designs, a common practice is to handle exceptions in the data tier to log details for troubleshooting purposes and ensure the integrity of the database, but then propagate the error to the calling application tier, which includes its own exception handling logic. 
+So far, you've used a TRY/CATCH block to handle an error gracefully. The client application that calls the stored procedure does not encounter an exception. In multi-tier application designs, a common practice is to handle exceptions in the data tier to log details for troubleshooting purposes and ensure the integrity of the database, but then propagate the error to the calling application tier, which includes its own exception handling logic.
 
 1. Return to the query used to create the stored procedure, and alter the procedure code to print the error number and message, like this:
 
diff --git a/Instructions/Labs/13-implement-transitions-in-tsql.md b/Instructions/Labs/13-implement-transitions-in-tsql.md
@@ -1,13 +1,13 @@
----
-lab:
-  title: Implement transactions with Transact SQL
-  module: Additional exercises
-  description: In this exercise you'll use a transaction to ensure that when a row is inserted into the Customer and Address tables, a row is also added to the CustomerAddress table to create a link between the customer record and the address record. If one insert fails, then all should fail.
-  duration: 72 minutes
-  level: 100
-  islab: true
----
-
+---
+lab:
+  title: Implement transactions with Transact SQL
+  module: Additional exercises
+  description: In this exercise you'll use a transaction to ensure that when a row is inserted into the Customer and Address tables, a row is also added to the CustomerAddress table to create a link between the customer record and the address record. If one insert fails, then all should fail.
+  duration: 30
+  level: 100
+  islab: true
+---
+
 # Implement transactions with Transact SQL
 
 In this exercise, you'll use transactions to enforce data integrity in the **AdventureWorks** database.
@@ -38,7 +38,7 @@ In this exercise you'll use a transaction to ensure that when a row is inserted
 
     *Conversion failed when converting date and/or time from character string.*
 
-1. Create a new query and enter the following code into the new query window: 
+1. Create a new query and enter the following code into the new query window:
 
     ```sql
     SELECT TOP 1 c.CustomerID, c.FirstName, c.LastName, ca.AddressID, a.City, c.ModifiedDate
@@ -110,7 +110,7 @@ Lower level errors can require that you explicitly handle the error and rollback
         VALUES (IDENT_CURRENT('SalesLT.Customer'), IDENT_CURRENT('SalesLT.Address'), 'Home', '16765338-dbe4-4421-b5e9-3836b9278e63', GETDATE());
     
     COMMIT TRANSACTION;
-    ``` 
+    ```
 
 1. Run the modified code. This time, a different error (with a lower severity level) occurs:
 
