SQL Server Error 207

Why it happens

Error 207 is a name resolution failure, not a syntax failure. The query is grammatically valid, so SQL Server accepts its shape, but when it tries to bind each column reference to a real column in the tables in scope it cannot find one that matches. The message names the offending identifier: Invalid column name 'emial'. That name is your fastest clue, because it is exactly the text SQL Server could not resolve.

The most common cause is a simple typo, such as emial for email. Close behind are qualifier problems: the column exists but lives in a different table in the join, or you referenced it without a prefix and no table in scope actually has it. Because the error is severity 16, it is a normal, catchable error that you fix by correcting the statement, not a server problem.

A subtler cause is scope. A column alias you define in the SELECT list is not visible in the WHERE clause, GROUP BY, or elsewhere in the same SELECT, so referencing it there raises 207. The same happens after a column is renamed or dropped, or when application code runs against a database where the expected schema change has not been deployed yet.

Examples

A misspelled column name

CREATE TABLE dbo.Users (
    id    INT PRIMARY KEY,
    email NVARCHAR(255)
);

-- 'emial' is a typo for 'email'
SELECT id, emial FROM dbo.Users;

Msg 207, Level 16, State 1, Line 7
Invalid column name 'emial'.

Using a SELECT alias in WHERE

-- full_name is defined in the SELECT list, but the alias
-- is not visible in WHERE, so 207 is raised.
SELECT first_name + ' ' + last_name AS full_name
FROM dbo.Users
WHERE full_name LIKE 'A%';

Msg 207, Level 16, State 1, Line 5
Invalid column name 'full_name'.

Column belongs to a different table in the join

-- CustomerId lives on Orders, not Users, and the
-- unqualified reference cannot be resolved.
SELECT u.id, CustomerId
FROM dbo.Users AS u
JOIN dbo.Orders AS o ON o.UserId = u.id;

Msg 207, Level 16, State 1, Line 3
Invalid column name 'CustomerId'.

How to fix it

-- List the real column names for the table
SELECT name
FROM sys.columns
WHERE object_id = OBJECT_ID('dbo.Users');

-- Or inspect the whole table
EXEC sp_help 'dbo.Users';

-- Then use the correct name
SELECT id, email FROM dbo.Users;

SELECT u.id, o.CustomerId
FROM dbo.Users AS u
JOIN dbo.Orders AS o ON o.UserId = u.id;

-- Repeat the expression in WHERE
SELECT first_name + ' ' + last_name AS full_name
FROM dbo.Users
WHERE first_name + ' ' + last_name LIKE 'A%';

-- Or expose the alias through a CTE
WITH named AS (
    SELECT first_name + ' ' + last_name AS full_name
    FROM dbo.Users
)
SELECT full_name FROM named WHERE full_name LIKE 'A%';

-- Confirm the column now exists in this database
SELECT COLUMN_NAME
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'Users' AND COLUMN_NAME = 'email';

How to prevent it

Use consistent, predictable naming across your schema so a column is easy to spell from memory, and always qualify columns with a table alias in any query that touches more than one table. That single habit prevents both the typo class and the wrong-table class of 207. For the fundamentals, see the SQL syntax guide.

Deploy schema changes before the code that depends on them, and keep environments in sync so a column your query expects actually exists where the query runs. When you are learning the language, working through the SQL tutorial builds the muscle memory for naming and qualifying columns correctly.

Common questions