SQL Server Error 208

Why it happens

Error 208 means SQL Server tried to bind your statement to an object and could not find one that matches the name you wrote. The name in quotes, for example dbo.Custmers, is exactly what the parser looked for and failed to locate. Because the object cannot be resolved, the whole statement is stopped at compile time with severity 16, a normal user-correctable error.

The most common cause is simply a typo in the object name. Just as common is being connected to the wrong database, so the object exists but not where you are looking, or the object living in a schema other than dbo while you referenced it with no schema or the wrong one. When you write an unqualified name, SQL Server looks in your default schema, which may not be where the object lives.

The object may also have been dropped or renamed since the query was written, or you may be querying a temporary table that no longer exists or is out of scope for the current session. In every case SQL Server has nothing to bind the name to, so it reports the name back to you as invalid.

Examples

A misspelled table name

-- The table is dbo.Customers, but the query misspells it.
SELECT id, name
FROM dbo.Custmers;

Msg 208, Level 16, State 1, Line 3
Invalid object name 'dbo.Custmers'.

An object in a non-dbo schema referenced without its schema

-- The table really is Sales.Orders, but it is referenced
-- with no schema, so SQL Server looks in the default schema.
SELECT order_id, total
FROM Orders;

Msg 208, Level 16, State 1, Line 4
Invalid object name 'Orders'.

A temp table that is out of scope

-- The temp table was created in another session or already
-- dropped, so it cannot be resolved here.
SELECT * FROM #StagingRows;

Msg 208, Level 16, State 1, Line 3
Invalid object name '#StagingRows'.

How to fix it

SELECT s.name AS schema_name, o.name AS object_name, o.type_desc
FROM sys.objects AS o
JOIN sys.schemas AS s ON s.schema_id = o.schema_id
WHERE o.name = 'Customers';

-- Option A: change the current database
USE MyDb;
SELECT id, name FROM dbo.Customers;

-- Option B: fully qualify the name
SELECT id, name FROM MyDb.dbo.Customers;

SELECT order_id, total
FROM Sales.Orders;

IF OBJECT_ID('dbo.Customers', 'U') IS NULL
    CREATE TABLE dbo.Customers (
        id   INT PRIMARY KEY,
        name NVARCHAR(100)
    );

IF OBJECT_ID('tempdb..#StagingRows') IS NULL
    CREATE TABLE #StagingRows (id INT, name NVARCHAR(100));

SELECT * FROM #StagingRows;

How to prevent it

Always reference objects with a two-part schema.object name so name resolution never depends on the caller default schema. This alone prevents most 208 errors caused by objects that live outside dbo.

Deploy objects before the code that uses them, keep schemas consistent across environments, and confirm you are connected to the intended database before running a query. For the rules behind identifiers and qualification, see the SQL syntax guide and the SQL tutorial.

Common questions