This video sets expectations and the course's goals. Explore the common foundations and the differences from part one, and the fact that part two has a higher difficulty level.
- [Instructor] So, joking aside, I really meant it when I said you should watch part one first. Even if you watched it just a few weeks ago, but don't feel 100% confident or don't remember everything, it really won't hurt to go through the chapters you found challenging one more time. I'm not going to repeat the materials from part one. And this also includes the introductory chapters about the terminology, the demo database, using the code files, the GitHub repo and DB fiddle. But we must keep things interesting, so there are a few exceptions. First, I'm going to use my new favorite IDE, Microsoft's open source, Azure Data Studio. I like that it has a minimalist user interface and that it supports both SQL Server and Postgres so I can show you the differences easily side by side. It's an awesome tool, give it a try. In part one, I typed most of the demo queries as I was demoing them. Now, they were relatively short, but now we're going to use more complex and longer queries. So I reserve the right to copy paste the code sections to save valuable time. I will highlight the important sections, but I'm not going to spoon feed you each character. And if you find it harder to follow, feel free to pause the video as frequently as you need and read the code at your own pace. Second, as promised in the introduction video, I have turned the difficulty level up one notch. No pain, no gain. Third, get ready for a bit more of relational theory, not much. In part one, I touched briefly on some aspects of the relational model but now we're going to take it a little bit further and I'm going to give you the broader picture. I'm sure this will help you remember the subtleties much better. The key to success is understanding, not memorizing. So, be patient with the theoretical parts, it will pay off. Forgive me students for I have sinned. In previous courses, I've used the term common table expressions or CTE. I recently had the pleasure of reading the ANSI SQL standard for this feature, and was surprised to learn that the term that I've been using all these years simply isn't correct. Although SQL Server, Postgres, and a few major vendors use it, the correct term according to the standard is the with clause. So that's what I'm going to use from now on. And this isn't all, but I've spent enough time for the introduction, so we'll cross the remaining bridges when we reach them. Now, let's get down to business.
This course was created by Ami Levin. We are pleased to offer this training in our library.