SQL (often pronounced "sequel") is a language for asking questions of databases. It looks technical at first, but it reads surprisingly close to plain English. If you can describe what you want from a spreadsheet, you can learn the basics of SQL.
Databases in one paragraph
A database stores information in tables, much like spreadsheet tabs. Each row is a record (one order, one customer) and each column is a field (order date, total, country). SQL lets you pick, filter, group and sort those rows without scrolling through them.
The five clauses that cover most questions
SELECT and FROM: choose columns
SELECT customer_name, order_total FROM orders; returns two columns from the orders table.
WHERE: filter rows
SELECT * FROM orders WHERE country = 'Canada'; keeps only Canadian orders. You can combine conditions with AND and OR.
ORDER BY: sort
... ORDER BY order_total DESC; lists the largest orders first.
GROUP BY: summarize
SELECT country, SUM(order_total) FROM orders GROUP BY country; totals revenue for each country. This is the SQL version of a pivot table.
Aggregate functions
COUNT, SUM, AVG, MIN and MAX work just like their spreadsheet cousins.
A complete business question
"Which five products generated the most revenue this year?"
SELECT product, SUM(order_total) AS revenue FROM orders WHERE order_date >= '2026-01-01' GROUP BY product ORDER BY revenue DESC LIMIT 5;
Read it aloud: select product and total revenue, from orders, this year only, grouped by product, sorted by revenue, top five. That is the whole query.
A gentle look at JOIN
Often information lives in two tables: orders and customers. A JOIN connects them using a shared column such as customer_id, similar to a lookup in a spreadsheet. Beginners only need to understand the idea; the syntax becomes familiar with practice.
Why non-technical people learn SQL
- You can answer your own questions instead of waiting for a report.
- You understand what analysts mean when they talk about data sources.
- Many dashboard tools use SQL-like logic behind the scenes.
Tips for learning
- Write the question in English first, then translate clause by clause.
- Start with small results; add
LIMIT 10while exploring. - Expect typos. A missing comma is the most common error.
Week 2 of our course, Asking Questions with SQL, practices these clauses with customer and order data. Our resources page also includes a short SQL glossary.
