SQL Comments
Explained for Beginners

SQL queries can be simple. But real SQL work gets complicated fast.

A small query might be easy to understand. A 200-line business analysis query with multiple joins, filters, calculations, and subqueries? Not so much.

That is where SQL comments help. SQL comments let you explain your logic directly inside your queries. If you are learning SQL for data analysis, interviews, or real projects, comments are a habit worth building early. Because writing SQL is one skill. Writing SQL that humans can understand later is another.

This is one of the simplest SQL concepts—but one of the most underrated.

SQL comments are notes written inside SQL code that the database ignores. They help explain what your query is doing.

-- Get active premium customers
SELECT *
FROM customers
WHERE is_active = TRUE
AND is_premium = TRUE;

The comment -- Get active premium customers is ignored by SQL execution. It exists only for humans.

Beginners often skip comments. That works when your query is tiny. But analyst queries quickly become complex.

-- High-value customers since Jan 2025
SELECT
   c.customer_name,
   SUM(o.revenue) AS total_revenue
FROM customers c
INNER JOIN orders o
ON c.customer_id = o.customer_id
WHERE o.order_date >= '2025-01-01'
AND o.status = 'Completed'
GROUP BY c.customer_name
HAVING SUM(o.revenue) > 50000;

You may understand it now. But later? Or if a teammate opens it? Comments help. Much clearer.

Future you counts as another person.

Single-line comments begin with --. Everything after that on the same line is ignored.

-- Pull customer data
SELECT *
FROM customers;

How Single-Line Comments Work:

SELECT *
FROM customers
-- Only active users
WHERE is_active = TRUE;

Multi-line comments use /* ... */. Everything inside gets ignored.

/*
Revenue analysis
Excludes refunds
Includes only completed orders
*/
SELECT *
FROM orders;

One of the most practical uses. Suppose a query is failing and you want to isolate the issue. You can temporarily disable parts:

SELECT
   customer_id,
   SUM(revenue)
FROM orders
-- WHERE status = 'Completed'
GROUP BY customer_id;

Now the filter is disabled. Fast debugging.

Commenting Out Multiple Lines

/*
SELECT customer_id,
    revenue,
    order_date
*/

Bad comments are too obvious. -- select data is useless. Better: -- Exclude internal employee accounts.

1. Write a single-line comment.
2. Write a multi-line comment.
3. Temporarily disable a WHERE clause using comments.

What Comes Next?

Now you understand SQL readability. Next comes SQL clauses. Because clauses are the building blocks that define query structure. This is where SQL query composition becomes clearer.

SQL comments seem simple. But they dramatically improve maintainability.

Strong analysts do not just write working SQL. They write understandable SQL.