Skip to main content

Common Mistakes in SQL

This article is a complementary resource to the Learn SQL Basics course.

Common Mistakes in SQL

When you're just starting out with SQL, it's easy to make mistakes. From typos to referencing wrong tables, these common errors can slow you down and lead to frustration.

But don't worry–we're here to help!

In this article, we'll explore some of the most common mistakes beginners make when working with SQL.

Let's get started.


Suppose we have a table Customers with the following data:

Customers

customer_id first_name last_name
1 John Doe
3 Jane Smith
4 Michael Johnson

Now, let's identify the common mistakes people make when working with SQL.

1. Using the Wrong Table Name

A common mistake among beginners and proficient developers is referencing a table that doesn't exist. This often happens due to typos or confusion about table names.

For example, you're trying to retrieve all data from the above table Customers.

If you mistakenly write:

-- Gives an error

SELECT *
FROM Customer; 

This results in an error, as the table name Customer doesn't exist.

Correction

-- Retrieve all data from Customers

SELECT *
FROM Customers; 

Note: Always verify table names to avoid errors.


2. Using the Wrong Column Name

Referencing a column that doesn't exist in the table is another common mistake. The above table Customers contains the columns customer_id, first_name, and last_name.

Example

-- The column "id" does not exist

SELECT id, first_name
FROM Customers;

Correction

-- Correct column name

SELECT customer_id, first_name
FROM Customers; 

Note: Always verify your table and column names before running a query to avoid these errors.


3. Misspelling Keywords and Identifiers

SQL is unforgiving with typos. Misspelling keywords like SELECT, FROM, or table and column names can lead to errors.

Example

-- SELCT is misspelled

SELCT first_name, last_name 
FROM Customers;

Correction

SELECT first_name, last_name
FROM Customers;

Note: Check for typos before running queries.


4. Forgetting Commas Between Columns

Forgetting commas when selecting multiple columns causes syntax errors, making queries fail. Therefore, when selecting multiple columns, we must use a comma.

Example

-- Missing a comma between columns

SELECT first_name last_name    
FROM Customers;

Correction

-- Include the required comma

SELECT first_name, last_name    
FROM Customers;

Note: Double-check column lists for commas to avoid errors.


Mistakes are part of the learning process, so don't get discouraged. By avoiding these common mistakes and with some practice, you'll soon write clean, effective SQL queries confidently.