What does Msg 208 mean in SQL Server?

Msg 208, "Invalid object name," means SQL Server's compiler couldn't find a table, view, or other object with that name in the current database and schema context — it's a compile-time check, not a data problem.

Why does a stored procedure compile but fail later with this error?

SQL Server uses deferred name resolution for objects referenced inside a stored procedure body — it doesn't verify every table exists until that specific statement actually executes, so a typo in a rarely-used branch can go unnoticed for a long time.

Why can't my second query window see a temp table from my first one?

A local temp table (#name) is scoped to the session that created it. Each new query window in SSMS opens its own session, so it can't see another window's #temp tables — use a global temp table (##name) for cross-session visibility.

Is SQL Server case-sensitive?

By default, no — most instances use a case-insensitive collation. But if a database or column explicitly uses a case-sensitive collation (one ending in _CS), unquoted case mismatches will fail to resolve.

How do I check which schema a table is really in?

Query sys.tables joined to sys.schemas, or run sp_help 'TableName' — both show the schema SQL Server actually recorded the object under.

Fix "Invalid Object Name" in SQL Server (Msg 208)

sqlfmt▍

Fix "Invalid Object Name" in SQL Server (Msg 208) — sqlfmt

Unlike PostgreSQL, SQL Server defers name resolution inside stored procedures — a batch can reference a table that doesn't exist yet at creation time and only fail when it actually runs. That's part of why "Invalid object name" shows up at unexpected moments. Here's what's really going on.

Key takeaways

SQL Server tables default to the dbo schema — if yours was created under a different schema, an unqualified reference won't find it.
#temp tables are scoped to the session (or stored procedure call) that created them; a second connection or a later batch can't see them.
SQL Server defers name resolution for objects referenced inside stored procedures, so a typo can sit undetected until that code path actually executes.
sys.tables joined to sys.schemas (or sp_help) shows exactly what schema an object really lives in.

Cause 1: Missing or wrong schema prefix

SQL Server resolves an unqualified table name against the caller's default schema, which is dbo unless explicitly changed. A table created under a different schema needs to be referenced with that schema prefix.

Schema mismatch

CREATE TABLE sales.Orders (id INT PRIMARY KEY);

SELECT * FROM Orders;        -- Msg 208: Invalid object name 'Orders'
SELECT * FROM sales.Orders;  -- works

How to Fix "Invalid Object Name" in SQL Server

Quick answer

FAQs

What does Msg 208 mean in SQL Server?

Why does a stored procedure compile but fail later with this error?

Why can't my second query window see a temp table from my first one?

Is SQL Server case-sensitive?

How do I check which schema a table is really in?

How to Fix MySQL Error 1146: Table Doesn't Exist

PostgreSQL “column does not exist”: Causes and Fixes

How to Fix “Conversion Failed When Converting” in SQL Server

Key takeaways

Cause 1: Missing or wrong schema prefix

Cause 2: A #temp table out of scope

Cause 3: Deferred name resolution inside stored procedures

Cause 4: Wrong database context

Cause 5: Case-sensitive collation

How to fix it

Quick answer

FAQs

What does Msg 208 mean in SQL Server?

Why does a stored procedure compile but fail later with this error?

Why can't my second query window see a temp table from my first one?

Is SQL Server case-sensitive?

How do I check which schema a table is really in?

Keep reading

How to Fix MySQL Error 1146: Table Doesn't Exist

PostgreSQL “column does not exist”: Causes and Fixes

How to Fix “Conversion Failed When Converting” in SQL Server

Key takeaways

Cause 1: Missing or wrong schema prefix

Cause 2: A #temp table out of scope

Cause 3: Deferred name resolution inside stored procedures

Cause 4: Wrong database context

Cause 5: Case-sensitive collation

How to fix it

Related reading