»»» Used copies of this book may be missing critical digital resources. «««
»»» Updated 2020 edition «««
The ability to write SQL is one of the most in-demand job skills. Are you prepared?
It's easy to find basic SQL syntax information online. What's hard to find is challenging, well-designed, real-world problems—the type of problems that come up when you're dealing with data. Learning how to solve these problems will give you the skill and confidence to step up in your career.
With SQL Practice Problems, you can get that level of experience by solving sets of targeted problems. These aren't just problems designed as syntax examples. These are the most common problems you encounter when you deal with data.
You will get real world practice, with real world data. I'll teach you how to “think” in SQL, how to analyze data problems, figure out the fundamentals, and work towards a solution that you can be proud of.
Can I run SQL Practice Problems on a Mac? No, it requires a computer with Microsoft Windows. I also offer a Professional package at SQLPracticeProblems.com which is suitable for both Windows and Mac.
How important is the real-life, hands-on problem solving that you can find in SQL Practice Problems?
You can watch videos online that will walk you through various aspects of databases, and SQL. And you can read up on SQL syntax and keywords, and review sample code.
But...to really absorb and be able to apply your learning, you need to solve real-world problems. Being presented with a SQL problem, and working through that problem (with hints, if necessary) will help you understand and remember like nothing else.
What do you get when you buy SQL Practice Problems?
Setup instructions for Microsoft SQL Server Express Edition and SQL Server Management Studio (Microsoft Windows required). Both are free downloads.A customized practice database, with a video walk-through on setting it up.Practice problems - 57 problems that you work through, step-by-step. There are targeted hints if you need them, which help guide you through the question.Answers and a short, targeted discussion section on each question, with alternative answers and tips on usage and good programming practice.What does SQL Practice Problems not contain?
Complex descriptions of syntax. There's just what you need, and no more.The differences between every single SQL variant (MS SQL Server, Oracle, MySQL, etc). The practice problems are set up with Microsoft SQL Server, and the differences are minor and easy to find online.Details on Insert, Update and Delete statements. The hardest thing to learn in SQL is how to write Select statements that return complex data. Other components of SQL are relatively easy.From customer "Probably the most useful technical book I've used! Challenging problems with appropriate hints - use as needed. She should be writing other books."- A. J.
"I have numerous books on SQL, and have taken courses from people with lots of experience with data and SQL.
عموما کتابای تکنیکال رو نمیزنم تو گودریدز، ولی واسه اینکه به چالش 2022 رسیده باشم میزنم :))) سوالای sql بود و اکثرا ساده بودن راجع به کوئری نویسیه، یعنی از زیر ساختای اس کیو ال و ایندکس کردن و اینا چیزی نمیگه
I went straight to the "Advanced Problems" and I was a bit confused at first since I was not acquainted with the Northwind database. I had to Google the data model schema and after 3-4 exercises I was all set !
I enjoyed how the book is constructed. It starts with simple exercises and really builds upon the various challenges we encounter to create new and manageable problems. The perfect balance of difficulty made those problems a stimulating challenge for me.
I learned a lot, and I think some exercises were brilliant (n°51 and n°57). The expression used for the JOIN in exercise 51 is definitely something I will be using and the LEAD function in exercise 57 blew my mind haha.
However, I still think that some aspects of the book could be improved, especially when it comes to the solutions proposed. Although common table expressions are nice to structure the code (and are way clearer than nested SELECT), the author is sometimes creating CTEs that are not necessary and could be replaced by a single line of code.
For instance, in problem 50, there is no reason to have 2 CTEs in order to calculate the column "PercentTotal". The command SUM(COUNT(*)) OVER () can do the trick.
Same goes for problem 49, I think there is no reason to include a CTE. The following query works well and is simpler to read:
I also noticed some elements that were not necessary in my opinion. For instance, in problem 36, there is no reason to JOIN the Orders and OrderDetails tables since we simply want to calculate the number of ProductID per OrderID. The OrderDetails table is already at the desired level of granularity.
Not a bad book! This book focuses purely on Microsoft SQL Server and more specifically DQL (Data Query Language) aspect of SQL i.e. basically just querying the database; no inserts, no creates etc.
I found it pretty easy for someone using SQL (DQL) for over 10 years (even most of the advanced topics). However, I found it useful as a refresher on writing the sort of queries one might need in a typical corporate environment.
For the beginner to even intermediate SQL skill level I think it is an excellent book and it really gets your hands data right from the outset by working on real questions about data a business user might tap you on the shoulder to ask you about.
The concept is great though! Getting you practising on a real case studies as you might encounter in your workplace.
This book has a very good set of questions for people who have some experience with SQL but aren't experts yet. Also, the amount of questions is very manageable for a week of focused studying.
Beginner and Intermediate problems were too simple for me. However, I enjoyed the advanced problems. Got to learn many things. Now I have more weapons in my Sql arsenal :)
Either my level has long since reached this book, or the book itself is superficial. I was thinking of raising my level of knowledge beyond advanced . I didn't learn anything new in the end.