SQL and database: what's the difference?

Language or database engine?

SQL describes how to query and structure relational data. A database engine understands this language, stores the information and executes the queries.

Much of SELECT, WHERE, JOIN and GROUP BY are common. The differences appear more in row limiting, date functions, types, auto-increment and advanced write operations.

The query explained

Start by defining what a row of the result should represent. This decision determines the necessary columns, groupings, and controls.

The following example isolates the main mechanism. Run it, observe the result, then change one clause at a time to understand its effect.

SELECT produit, prix
FROM produits
ORDER BY prix DESC
LIMIT 5;

Read the result like an analyst

Learn the common core first: level of detail, filters, joins, and aggregations. These skills transfer better than memorizing a specific function of a tool.

When you change engines, check its documentation for trouble spots and test the query on a small dataset.

• Identify the target engine.
• Check the syntax of dates and pagination.
• Control the types and behavior of NULL.
• Test non-standard functions.

Errors that distort the analysis

A query can be valid without correctly answering the question. The most costly errors are often silent: wrong perimeter, multiplied line or missing value interpreted as zero.

Before sharing the result, compare it to a small hand-calculated sample and keep the scope definition with the query.

• Present SQL as a unique software.
• Assume that a function exists with the same name everywhere.
• Copy a LIMIT syntax into another engine without adaptation.
• Confusing syntactic compatibility with identical business results.

Get into practice

Start by writing portable queries, then explicitly note each dialect difference encountered.

The SQL simulator of SQL.tn only runs read queries on dummy data in your browser. You can try multiple writes and compare their results without installing any software.