SQL was one of those things I kept pushing down my learning list.

I knew databases were important, but whenever I thought about SQL, I imagined tables, rows, and something that looked suspiciously like Excel. It never seemed exciting enough to prioritize.

Recently, I decided to stop avoiding it and started working through an introductory SQL course. What surprised me wasn't that SQL became easy overnight. It was how quickly the fundamentals started making sense once I began writing queries myself.

SQL Felt More Like English Than Programming

It first starts with special words called clauses
CLAUSES are reserved words that when used give the system a particular task to perform in respect to the table
examples are:

SELECT * FROM employees;

Breaking it down helped:

SELECT is a clause that tells the database what data to return.

  • (Wildcard character) means all columns. FROM is a clause that specifies the table.

So the query simply means:

Show me everything from the employees table.

That was my first realization: SQL isn't about telling the database how to find data. It's about describing what data you want.

Tables Started Making Sense

I also learned that databases organize information into tables made up of rows and columns. Each row represents a record, while each column stores a specific piece of information. Once I understood that structure, queries felt much less abstract.

Creating and Adding Data

Creating a table looked like this:

CREATE TABLE employees (
id INTEGER,
name TEXT,
role TEXT
);

each columns follow a structure namely.

column_1 data_type,
column_2 data_type,
column_3 data_type.

which is the column parameters with its name and associated parameters.

This defines the structure of the data.

Then I could add information using:

INSERT INTO employees
VALUES (1, 'David', 'Developer');

This would be a good example with parameters of artistes filled in

At that point the workflow clicked:

CREATE TABLE **creates the structure.
**INSERT INTO adds records.
SELECT retrieves records.
**WHERE **Quickly Became My Favorite Clause

I found the WHERE clause especially useful:

SELECT * FROM employees
WHERE role = 'Developer';

Instead of returning every record, it filters results based on a condition.

It sounds simple, but this was the moment I started seeing why SQL is so powerful.

Small Mistakes Can Have Big Consequences

I also learned that SQL commands can be deceptively simple.

UPDATE employees
SET role = 'Senior Developer'
**WHERE **id = 1;

The WHERE clause limits the update to a specific row.

Without it:

UPDATE employees
SET role = 'Senior Developer';

every row gets updated.

The same applies to:

DELETE FROM employees
WHERE id = 1;

versus:

DELETE FROM employees;

One deletes a record. The other deletes all records.

That lesson stuck with me.

Databases Have Rules Too

Toward the end of the module, I learned about constraints like PRIMARY KEY, NOT NULL, and UNIQUE. These rules help databases maintain data quality and prevent invalid information from being stored.

Final Thoughts

My biggest takeaway so far is that SQL isn't nearly as intimidating as I imagined.

Most of the keywords are surprisingly descriptive. SELECT selects, INSERT inserts, UPDATE updates, and DELETE deletes.

I'm still early in the learning process, but SQL already feels less like mysterious database magic and more like a practical tool that every developer should know.

Sometimes the hardest part isn't learning the technology.

It's finally starting.