I have an embarrassing confession. Promise not to tell anyone?

I’ve been a Senior Data Analyst for 10 years….

And….I still don't know even half of all SQL commands 🙈

I have never used a "lateral join." I don't touch "cursors." And if you asked me to set up a SQL trigger right now, from scratch? I’d fail.

Here’s why that all is actually a good thing…

(audio version of this newsletter)

SQL is like an iceberg.

Some SQL commands you hear about a lot - like the ice you see above the water. But there are tons of commands hidden deep under the water.

Most beginners try to learn the whole iceberg. They think they have to become SQL master’s.

That is a complete waste of time.

If you want to land a job, you don't need to be a SQL guru. You just need to master “The Core Slice” - the small set you will use all the time as a Data Analyst

I teach “The Core Slice” in two weeks in my bootcamp. That is about 30 hours of work. And if you focus, you can be ready to start interviewing in about three weeks.

So what commands are in “The Core Slice”?

The Only 17 SQL Commands You Actually Need

Ready for the list? Here it is:

• The basics: SELECT, FROM, WHERE

• Filters: LIKE, AND, OR, NOT

• Math stuff: COUNT, SUM, AVG, MAX, MIN

• Grouping: GROUP BY, HAVING

• Logic: CASE WHEN

• Joins: JOIN

• Clean up and sort: DISTINCT, ORDER BY

• Common advanced: WITH, PARTITION BY

• Text: CONCAT

That's it. Those 17 commands will solve about 90 percent of the problems a data analyst actually faces on the job.

Could you add a few more? Sure. UNION helps. Date functions help too. Maybe RANK. But the point is simple: starting small is good enough. You don't need to learn 100 commands. You need to learn 17 really well.

Stop Trying to Memorize Everything

I forget SQL syntax all the time. Like, embarrassingly often.

And it's fine. Because when you're on the job, nobody is standing over your shoulder making sure you remember every detail.

You have Google. You have ChatGPT. You have editors that suggest syntax for you.

The need for SQL memorization is going down. Fast.

Now, interviews? That's different. Some interviewers treat SQL like a memory test. If you don't know it, you're out. I hate that style of interview, but it exists. So just be ready for it.

But once you're on the job? Forget away. Nobody cares. They care about results.

Here are some other important SQL things you should know…

What They Don't Teach You in Online Courses

1. You need an IDE or workbench.

SQL is not like Excel. You can't just download it and double click to open it.

You need something called an IDE (or workbench) to actually use SQL. It's like a companion software. And setting it up? It's annoying. Every single time.

I've done it a hundred times and I still hate it.

That's why in my bootcamp, we actually start with a cloud version of SQL first. So students can focus on learning the language before they have to deal with the painful download process.

2. You need to use LIMIT.

When you run a SQL query, it will return ALL matching rows. That could be 10 rows. Or 10 million rows.

If you try to return 10 million rows, your computer will cry. And you'll sit there waiting forever.

So here's the trick. Always use LIMIT at the end of your query when you're testing. Start with LIMIT 10. Then 100. Then 1,000. When it looks right, remove LIMIT.

Test small. Scale up. Save yourself hours of waiting.

3. Skip these commands

A lot of beginner tutorials teach you commands you will literally never use as a data analyst.

Things like INSERT, DELETE, UPDATE, GRANT, REVOKE.

Those are data engineering commands. Your job as an analyst is not to build or manage databases. Your job is to ask questions of the data. To query it.

So skip the database management stuff. Seriously. Don't waste your time. Focus on what actually gets you hired…

What does get you hired? Not SQL.

SQL won’t get you hired.

Getting great at SQL doesn't get you hired.

I know. That sounds crazy. But it's true.

Right now, if you're applying to data jobs and getting rejected, it's not because you're bad at SQL. It’s because your resume is not strong yet. Or your LinkedIn is weak. Or you have no portfolio. Or you're not networking.

SQL is just one piece of a much bigger puzzle.

I call it the SPN Method. Skills. Portfolio. Network.

You need all three to land a data job. Most people focus only on the S (skills). And SQL is just one part of that S.

So it's like 1 out of 15 parts of the puzzle.

If you're grinding SQL problems on LeetCode every day thinking it's going to magically land you a job, you're wasting your time.

You need to build projects. You need to connect with people. You need to tell your story.

So Here's What to Do

Learn the 17 commands. Put in 30 hours. Get comfortable. Then move on.

Build a portfolio project. Update your LinkedIn. Start networking.

Don't get stuck in the endless SQL grind. It's a trap.

The goal is not to be the best SQL writer in the world. The goal is to land a data job. And that takes more than just code.

P.S. If you feel like you've got the SQL basics down but aren't getting interviews, you need to fix your Portfolio and Network. I teach the full SPN method inside my Data Analytics Accelerator. 👔

DATA JOBS OF THE WEEK

Intern, Data Analyst (EVgo)
Link: https://www.findadatajob.com/jobs/intern-data-analyst-winter-spring-fa74b758

Junior Marketing Analyst (SmartFinancial)
Link: https://www.findadatajob.com/jobs/junior-marketing-analyst-353c830c

Data Analyst (Zearn)
Link: https://www.findadatajob.com/jobs/data-analyst-b824f3a6

Business Intelligence Engineer II (Amazon)
Link: https://www.findadatajob.com/jobs/business-intelligence-engineer-ii-central-strategy-operations-and-gtm-7b31e6f3

Principal Financial Analyst (Medtronic)
Link: https://www.findadatajob.com/jobs/principal-financial-analyst-portfolio-finance-operations-f8dbef20

📺 LATEST EPISODE

Or if you enjoy the audio version, you can listen to it here!

💡 If SQL Feels Confusing, Read This

Hey, it's Avery. Remember how I told you I wanted to introduce some new voices in the newsletter. This is my first time doing it :)

This is Trevor Maxwell. Trevor, take it from here!

👋 Hey, this is Trevor Maxwell,

I am an alumni from the DAA program. I’ve been working as a technical business analyst for 2 years now. I now also help Avery as a coach inside DAA, and I really want to help you break into this wonderful industry!

Learning SQL can be exciting. You run your first query, see a table appear, and think, “Wow, I’m doing it!” But then things get messy. The tables don’t connect the way you expect.

But I have good news to share:

This is normal. And if you understand the simple data concepts, your path into a data career becomes much smoother. I tried learning the advanced functions at first, hoping it would make me a great analyst, but the real secret is understanding what you are looking for.

Today, with AI, the tricky parts of SQL are easier than ever. AI can help you fix syntax, explain errors, and even write sample queries. The hard part isn’t typing the right function it’s knowing the question you’re trying to answer. Half the battle is understanding the data and why it matters.

If you learn how to clearly define what you want from the data, SQL becomes much simpler. Are you ready for even better news?

With a common transferable skill like communication you can be a great analyst. Great communication takes you farther than advanced SQL skills.

If you can talk clearly with your teammates, ask good questions, and explain your confusions then you will know what to look for. Even in technical roles, communication is one of your strongest tools.

Lastly I’ll say, don’t be afraid to explore tables, test ideas, and experiment. You have time. Play with the data. It will teach you a lot. Good analysts are curious, not perfect.

I love how the DAA Community culture promotes a concept of “Progress > Perfection”.

I know the SPN method works because you build projects, then you talk about them, and share them which helps you confidently communicate and get noticed.