I learned SQL the hard way. My first job, week two, my manager dropped a CSV on my desk with 40,000 rows and said, "tell me which customers haven't ordered in six months." I opened Excel. Excel froze. I cried a little inside. By the end of that week I knew three SQL queries, and one of those queries took my CSV problem and gave me an answer in about a second.

That was 2014. Today, in 2026, SQL is still the answer to that same problem. Frameworks come and go. JavaScript libraries rewrite themselves every Tuesday. But SQL just sits there, quietly running the world. Your bank account, your Swiggy order, your IRCTC ticket, your Instagram DMs. All of them talk to a SQL database somewhere.

This lesson is short on purpose. I want you to read it, then go play in the panel on the right and feel that little click in your brain when your first query returns the right rows. That feeling is the whole reason people fall in love with SQL.

A database is just organized stuff

Think of a database the way you think of a notebook with neat columns. You have rows (each customer is one row), and columns (name, phone, city). One table per kind of thing. Customers in a customers table. Orders in an orders table. Restaurants in a restaurants table. They link to each other using IDs.

That is it. That is a relational database. The word "relational" just means the tables relate to each other through IDs. There is no magic here. Anyone who pretends databases are hard is selling you a course.

SQL is the language you use to ask questions

When you want something out of a database, you write a sentence in SQL. The sentence almost reads like English.

SELECT name, city FROM customers WHERE city = 'Bengaluru';

Read it out loud. Select the name and city, from the customers table, where the city is Bengaluru. That is the whole query. The database reads it, figures out the fastest path to the answer, and hands you back rows.

This is why SQL has outlasted everything. Nobody had to invent a new syntax. The 1974 syntax still works. The query you write today would run on a database from 1990 with almost no changes. There is a quiet beauty to that.

Try it on the right (yes, really, right now)

The panel on the right is a real SQL database, running entirely inside your browser. Nothing gets uploaded anywhere. The data is a tiny Swiggy-style schema we will use for this whole track: customers, restaurants, orders.

Hit run to see your first query work. Then look at the Try this section below the playground. Three small assignments. Solve them one by one. Clippo (the paperclip on top) will react to each run. Learning is more fun when something is cheering you on.

If a query fails, read the error. The error is usually telling you exactly what is wrong, in the same English-ish syntax as SQL itself. Misspelled a column name? It will say so. Forgot a quote around a string? It will say so.

What is coming next

This track has more short lessons stacked behind this one. WHERE, ORDER BY, JOINs, GROUP BY, indexes, transactions. Each one builds on the last. By the end you will be writing queries that make a senior developer raise an eyebrow in a good way.

For now, just play. Get one assignment done. The first time your SELECT returns the exact rows you asked for, you are in.