What is SQL?

Hook: SQL is the translator between your app and stored data—interviewers love this question because it reveals whether you understand how software actually reads and writes information.

Question: What is SQL?

Answer: SQL stands for Structured Query Language. It is the standard language used to work with relational databases, where data is stored in tables made of rows and columns. With SQL, you can read data, insert new data, update existing data, delete data, and define or change table structure.

Interview-Ready Answer: I’d say SQL is the language used to communicate with relational databases. It is declarative, which means I describe what result I want, and the database decides how to get it. In practice, I use SQL to query data, change data, and manage schema, and the same core language is supported by systems like PostgreSQL, MySQL, SQL Server, and SQLite, even though each one has its own dialect.

Detailed Explanation:

What SQL really is

SQL is short for Structured Query Language. It is a declarative language, which means you describe the result you want instead of writing the exact steps to get it. A relational database stores data in tables, and tables are connected through keys, such as a customer id pointing to an order row.

How SQL works under the hood

1. You write a statement like SELECT name FROM customers WHERE id = 7.
2. The DBMS (database management system) parses it and checks the syntax.
3. It validates table names, column names, types, and permissions.
4. The optimizer chooses a plan, such as an index lookup, a table scan, or a join strategy.
5. The executor runs that plan against storage and returns the rows.
6. If the statement changes data, the database may also log the change so it can commit or roll back safely.

What you use SQL for

• Querying data: SELECT finds rows that match a condition.
• Changing data: INSERT, UPDATE, and DELETE modify rows.
• Defining schema: CREATE, ALTER, and DROP change tables and other objects.
• Permissions and transactions: many databases also use SQL for grants and transaction control.

These statement groups are often described as DDL (Data Definition Language) for structure and DML (Data Manipulation Language) for data. Some teams also mention DCL for permissions and TCL for transaction control.

SQL vs NoSQL

SQL is not the same thing as a database. It is the language; PostgreSQL, MySQL, SQL Server, and SQLite are database systems that implement it. A common interview point is that SQL databases tend to be best when your data is structured and relationships matter.

Use SQL when you need reliable structure, joins between related tables, transactions, and reporting. Use a NoSQL database when the shape of the data changes often or when access patterns are very simple and high-scale.

Performance and complexity

SQL itself is not one algorithm, so there is no single big-O number for every query. A query on an indexed column is often close to O(log n) because a B-tree index, a balanced tree structure, narrows the search quickly; a full table scan is O(n); and a bad join can approach O(n^2) if the plan must compare many rows. In real systems, the difference is huge: an indexed lookup may finish in a few milliseconds, while a scan of 10 million wide rows can take seconds.

Indexes speed reads but cost space and write time. Adding a few useful indexes can make hot queries much faster, but every extra index also adds maintenance work to INSERT, UPDATE, and DELETE.

Important edge cases

• NULL means missing or unknown, so = NULL does not work; you must use IS NULL.
• ORDER BY is required if you need a stable row order; without it, the database may return rows in any order.
• SQL dialects differ. The core language is standardized, but exact functions, types, and syntax can vary by database.
• SQL is not automatically safe. In application code, you must parameterize queries to avoid SQL injection, which is a security bug caused by building SQL strings unsafely.

Real-World Example:

Imagine an e-commerce checkout service on a flash sale. The service uses SQL to read inventory, create the order, and mark stock as reserved. A developer forgets to put the stock check and the update inside one transaction, so two buyers can read the same last item before either update is committed. In production, the symptom is overselling: the database ends up with negative stock, support tickets spike, and logs show duplicate order attempts plus slow query warnings if the inventory lookup is missing an index. Users see a spinner, then a confusing item unavailable message after payment already started, which is the kind of bug that ruins trust fast.

Follow-up & Tricky Questions:

• What is the difference between SQL and MySQL? SQL is the language; MySQL is a database system that implements a dialect of that language.
• Is SQL a programming language? It is a declarative, domain-specific language. Some databases add procedural extensions, but core SQL is mainly for describing data operations.
• What are DDL and DML? DDL defines structure with commands like CREATE and ALTER; DML changes data with commands like INSERT, UPDATE, and DELETE.
• What is a JOIN? A JOIN combines rows from two tables by matching related columns, such as customers and orders.
• Why are indexes important? Indexes speed up reads by narrowing the search path, but they consume storage and make writes a bit slower because the index must also be updated.
• Does NULL = NULL return true? No. NULL means unknown or missing, so equality does not apply; use IS NULL instead.
• Does SQL guarantee row order? No. If order matters, you must use ORDER BY; otherwise the database can return rows in any sequence.
• Is SELECT * always fine? Not really. It can pull extra columns you do not need and can break application code if the schema changes.

Common Mistakes:

• Thinking SQL is the database. Correction: SQL is the language; the database is the software that stores and manages data.
• Using = NULL. Correction: use IS NULL or IS NOT NULL.
• Forgetting ORDER BY. Correction: result order is not guaranteed unless you ask for it explicitly.
• Assuming every SQL database behaves exactly the same. Correction: the standard is shared, but functions, types, and edge behavior vary by dialect.

Memory Hook: Think of SQL like a restaurant menu: you point to the dish you want, and the kitchen decides how to cook it. You say what data you want, not how to find every row.

Cheat Sheet:

• SQL = Structured Query Language.
• It works with relational databases made of tables, rows, and columns.
• It is declarative: you state the result, not the algorithm.
• It handles querying, inserting, updating, deleting, and schema changes.
• Performance depends on the execution plan, especially indexes and joins.
• NULL, ORDER BY, and dialect differences are classic interview traps.

Practice Tasks:

• Create a students table and insert three rows.
• Write a SELECT that filters by one column and sorts by another.
• Add a second table and use a LEFT JOIN to find missing matches with IS NULL.