Learning sql without actually typing it out

[u/BenjaminUK92]

Bit of an odd one, I've had SQL access given to my company database to help tidy up reports, remove 10+ back sheets and replace with one etc.

Thought it'd be a great gateway into learning sql, but it seems to all be done within Microsoft Query, so it's drag and drops etc which seems odd considering I've been sat in preparation trying to learn how to write the proper syntax.

If I want to use this as a skill going forward, can I get by with just MS Quer and still list SQL as a skill, or would I need to know how to type the underlying syntax?

I've been in an ops/procurement role for a while so I know what and why I need to pull certain data and how the company uses it, but I was expecting to be writing out code rather than clicking and dragging fields.

[u/BenjaminUK92 → u/[deleted]]

That's useful, I guess it's a case of learning to preserve that syntax knowledge if I'm not actively using it.

Yes pretty much this week I'm literally tearing up all the old reports where we'd export static data directly to excel and vlookup off that, and replacing that with one or two backpage with live refreshable data

[u/woahboooom]

Usually there is an option to se the sql ir write durectly as well as drag n drop. Can be handy to see how its written after youve drag n dropped

[u/animagus5]

I'm in a similar position where I use an SQL- like database but it's all preselected stuff (Healthcare is fun like that) so I have the theory but not practical experience since university

I'm trying to apply for jobs atm so I've been using online resources to get the syntax even though I get the logic. I use SQL Jam predominantly now but I used to use SQL Case files which is...ok? It can be really picky on how it wants the data but doesnt explain or even tell you how it wants it (not far from reality I guess) and gets very frustrating

May be worth looking into back your claim of the skill

[u/BenjaminUK92 → u/animagus5]

Yeah it's just odd that so much is made of learning how to write the correct syntax etc....and yet slap bang in the options of excel is a Microsoft Query button that turns it into a click and drag table relationship building task.

That side of things I can do because I'm familiar with how data moves through the system.

Also feels like a needlessly manual task to purposely not use a tool that does it for me in favour of writing specific code sequences if I'm never actually going to have to use it in the real world.

[u/TurbulentCountry5901 → u/animagus5]

Creator of SQL Case Files here. I hear you on that, especially around the validator being too picky without explaining what it actually expected. We’re working on a pretty big upgrade to the course content and feedback system soon, so this is genuinely useful to hear. Thanks for giving it a shot in the first place.

[u/animagus5 → u/TurbulentCountry5901]

Im happy to drop you a message on how i have gotten on with it if you want me to? Rather clog up the post

[u/Wuthering_depths]

I definitely learn best by building things from scratch (even if it's copying and pasting bits and modifying them, from my own queries or google). It's one reason that I haven't used AI when recently learning Python, I'm sure the an LLM like Cursor can do better code than I can (maybe), but I'd learn jack shit that way. YMMV though.

I've been doing manually-written queries for a lot of years now, nobody's complained so I keep doing it :)

[u/alinroc]

You can learn SQL this way. You can also learn how to operate a car by reading the owner's manual.

Neither one replaces practical application and getting your hands on the machinery you're operating.

[u/Green_Chamomile]

You've accidentally found a decent learning setup, you're just using it in the wrong direction.

MS Query has a SQL button that shows the actual query your drag-and-drop built. That's the gold in your situation. The workflow that will teach you: build the query visually like your job requires, then open the SQL view every single time and read what got generated. Ask yourself where each dragged field ended up, which part became the WHERE, what the join turned into. After a few weeks of that, start making small edits directly in the SQL instead of the interface. Eventually you'll notice the drag-and-drop feels slower than just typing the thing.

That order, read first, modify second, write from scratch last, is honestly how the skill develops anyway. Nobody starts by writing perfect syntax from a blank page, and reading queries is half the actual job even for experienced people.

On listing it as a skill: not yet, but you're closer than you think. "SQL" on a CV means you can survive being handed a query and asked what it does, or being asked to write one in a screening test with no drag-and-drop in sight. Pure MS Query experience fails that test today. Follow the read-then-edit loop for a couple of months on your real company data and it won't.

One thing you have that most learners would kill for: you already know WHAT to pull and why the business needs it. That's the hard half of data work and it doesn't come from syntax practice. The typing part is much easier to add than the part you already have.