The SQL Sub-Languages: DDL, DML, DQL, DCL & TCL

Overview

SQL isn't one flat list of commands — every statement belongs to one of five sub-languages, grouped by what kind of thing it actually changes. DDL changes the schema itself. DML changes data. DQL reads data. DCL changes permissions. TCL controls where a transaction begins and ends. Knowing which sub-language a statement belongs to tells you its real blast radius before you run it — a `DROP TABLE` and a `SELECT` are both 'just SQL,' but they are not remotely the same kind of operation.

Why It Exists

This grouping isn't academic — it maps directly onto who should be allowed to run what, and how the database engine itself treats each kind of statement. Most engines auto-commit DDL immediately and separately from your transaction, many production teams route DDL through a reviewed migration tool instead of letting application code run it directly, and DCL is typically restricted to database administrators entirely. Understanding the five sub-languages is what lets you reason about a statement's risk before running it, instead of treating every line of SQL as equally safe.

Real World Example

In a typical order-processing system: a migration tool runs the DDL that created the `orders` and `customers` tables in the first place. The application runs DML (`INSERT`, `UPDATE`) to record new orders, and DQL (`SELECT`) constantly, to read them back. A database administrator runs DCL (`GRANT`) to give a new reporting service read-only access to the `orders` table, without giving it the ability to modify anything. And the order-placement code wraps its multi-step DML in TCL (`BEGIN` ... `COMMIT`), so that debiting inventory and creating the order row either both succeed or both roll back together.

Example Data

How It Works

• DDL (Data Definition Language) — CREATE, ALTER, DROP, TRUNCATE — defines and changes the schema itself: tables, columns, indexes, constraints.
• DML (Data Manipulation Language) — INSERT, UPDATE, DELETE — changes the data inside existing tables.
• DQL (Data Query Language) — SELECT — reads data without changing it (some references fold this into DML, but it's worth treating separately since it's the statement you'll write most often).
• DCL (Data Control Language) — GRANT, REVOKE — controls who can do what, at the permissions layer.
• TCL (Transaction Control Language) — BEGIN, COMMIT, ROLLBACK, SAVEPOINT — controls where a transaction's boundaries are, wrapping a group of DML statements so they succeed or fail together.

The Five Sub-Languages, One at a Time

CREATE TABLE orders (
  id INT PRIMARY KEY,
  customer_id INT NOT NULL,
  product TEXT NOT NULL
);

ALTER TABLE orders ADD COLUMN status TEXT DEFAULT 'pending';

DROP TABLE old_orders;

INSERT INTO orders (id, customer_id, product) VALUES (101, 1, 'Laptop');

UPDATE orders SET status = 'shipped' WHERE id = 101;

DELETE FROM orders WHERE id = 101;

SELECT id, product, status
FROM orders
WHERE customer_id = 1
ORDER BY id DESC;

GRANT SELECT ON orders TO reporting_service;

REVOKE INSERT, UPDATE, DELETE ON orders FROM reporting_service;

BEGIN;

UPDATE accounts SET balance = balance - 500 WHERE id = 1;
UPDATE accounts SET balance = balance + 500 WHERE id = 2;

COMMIT;

Diagram

Common Mistakes

Interview Questions

Production Best Practices

Comparison