SQL Server Error 4104

Error number

4104

Severity

16 (user-correctable error)

State

1

Product

Microsoft SQL Server Database Engine

Versions

All supported SQL Server versions (2016 to 2025), Azure SQL Database, Azure SQL Managed Instance

Category

Syntax & Object Resolution

Last reviewed

23 October 2026

What it means

Error 4104 means a name with a prefix, such as c.name or Customers.name, points at a table or alias that is not available at that point in the query.

A multi-part identifier is a column written with a prefix: alias.column, table.column or schema.table.column. While compiling the query, SQL Server binds each prefix to a table or alias in the FROM clause that is in scope. If the prefix matches nothing, the batch fails with 4104 at severity 16 before any row is read.

The most common surprise: once you give a table an alias, the alias replaces the table name for the rest of the query. After FROM dbo.Customers AS c, Customers.name no longer binds; only c.name does. A plain column name that does not exist raises error 207 instead.

Common causes

• A typo in the alias, or an alias that was renamed in the FROM clause but not everywhere else.
• Using the table name after giving the table an alias.
• An ON clause or WHERE clause that refers to a table joined later, or not joined at all.
• A reference to an inner query alias from outside it, for example a derived table column used with the wrong prefix.
• An UPDATE or DELETE with a join that names the target table instead of the alias used in its FROM clause.

Diagnose it

Read-only These queries only read metadata and dynamic management views. They do not change data, permissions or configuration, so they are safe to run first.

EXEC sp_describe_first_result_set
     N'SELECT c.name FROM dbo.Customers AS c;';

SELECT c.name AS column_name, t.name AS data_type
FROM sys.columns AS c
JOIN sys.types AS t ON t.user_type_id = c.user_type_id
WHERE c.object_id = OBJECT_ID(N'dbo.Customers')
ORDER BY c.column_id;

How to fix it

Each fix is labelled with what it changes. Try read-only checks and the least invasive fix first, and test changes outside production.

SELECT c.name
FROM dbo.Customers AS c;

SELECT c.name, o.total
FROM dbo.Customers AS c
JOIN dbo.Orders AS o ON o.customer_id = c.id;

UPDATE c
SET c.vip = 1
FROM dbo.Customers AS c
JOIN dbo.Orders AS o ON o.customer_id = c.id
WHERE o.total > 1000;

Examples

An alias that does not exist

CREATE TABLE dbo.Customers (id INT PRIMARY KEY, name NVARCHAR(100));

SELECT c.name
FROM dbo.Customers AS cu;  -- the alias is cu, not c

Msg 4104, Level 16, State 1, Line 3
The multi-part identifier "c.name" could not be bound.

The table name used after an alias

CREATE TABLE dbo.Customers (id INT PRIMARY KEY, name NVARCHAR(100));

SELECT Customers.name
FROM dbo.Customers AS c;  -- after AS c, only c.name binds

Msg 4104, Level 16, State 1, Line 3
The multi-part identifier "Customers.name" could not be bound.

An ON clause that names a table not in the query

CREATE TABLE dbo.Customers (id INT PRIMARY KEY, name NVARCHAR(100));
CREATE TABLE dbo.Orders (id INT PRIMARY KEY, customer_id INT, total DECIMAL(10,2));

SELECT c.name, o.total
FROM dbo.Customers AS c
JOIN dbo.Orders AS o ON o.customer_id = x.id;  -- x is not defined

Msg 4104, Level 16, State 1, Line 4
The multi-part identifier "x.id" could not be bound.

How to prevent it

Give every table a short, meaningful alias and prefix every column with it, especially in joins. Consistent aliases make wrong prefixes obvious in review and protect queries from ambiguous column errors (209) when tables gain columns later.

Build joins one table at a time and run the query as you go. For a refresher on join order and aliases, see the SQL joins guide.

Common questions

Learn more on CodeWithSQL

• SQL joins guide
• SQL joins lesson
• SQL SELECT statement explained with examples

Official documentation

• MSSQLSERVER_4104 (Microsoft Learn)
• FROM clause plus JOIN, APPLY, PIVOT (Transact-SQL)
• sp_describe_first_result_set (Transact-SQL)

Last technically reviewed 23 October 2026; examples and diagnostics run on SQL Server 2025 (17.0.1145.4). Message text checked against the engine's sys.messages catalogue.