Not an issue, just some feedback I'd like to go straight to the authors.

My student this week has said he really likes the challenge questions. I like them as well, they are a great part of the labs.

Thanks
Craig

Module: 01 (or more?)

Lab/Demo: Slide 9

Task: 00

Step: 00

The SQL query is not valid for AdventureWorksLT ( the database script provided). The course notes have too many AdventureWorks queries. All examples in PowerPoint/Skillpipe, Demos, and Labs should use the AdventureWorksLT database so students and instructors can run them in what is deemed the course database.

In Mod 1 Slide 9, Current Query:
SELECT OrderDate, COUNT(OrderID) AS Orders
FROM Sales.SalesOrder
WHERE Status = 'Shipped'
GROUP BY OrderDate
HAVING COUNT(OrderID) > 1
ORDER BY OrderDate DESC;

Suggest changing to (it is basically same query just fixed table and columns names):
SELECT OrderDate, COUNT(SalesOrderID) AS Orders
FROM SalesLT.SalesOrderHeader
WHERE Status = 5
GROUP BY OrderDate
HAVING COUNT(SalesOrderID) > 1
ORDER BY OrderDate DESC;

Slide 10, uses Production.Product ( this is from AdventureWorks)
Change the table reference to SalesLT.Product for all 3 queries.

I am sure I will find more through out the course.

Lab/Demo: 2

Task: Restrict results using TOP

It is best practice to always use parens with the TOP clause.

Replace multiple instances of:

SELECT TOP 20 Name, ListPrice

With:

SELECT TOP (20) Name, ListPrice

Links:
docs.microsoft.com
SQL Prompt

Lab/Demo: 3a

Exercise - Query multiple tables with joins

Description of issue

I noticed AS is sometimes capitalized, while other times it isn't.

For example:

SELECT p.Name As ProductName, c.Name AS Category
FROM SalesLT.Product AS p
JOIN SalesLT.ProductCategory As c
    ON p.ProductCategoryID = c.ProductCategoryID;

I know it doesn't make a difference in regards to running the code, but should it be consistent? Is there a reason it isn't? (I'm just learning SQL, so really don't know).

"We'll use the AdventureWorks database in this lab, so let's start by exploring it in Azure Data Studio."

I know it's a little thing, but this is bugging me. We are not using the AdventureWorks database; we are using the AdventureWorksLT database.