SQL Server: Invalid object name 'x'. (Msg 208)
The table/view doesn’t exist in the current database or schema.
Exact message you may see
Invalid object name
Seen on:
SQL
Meaning
Wrong database context (USE), missing schema prefix (dbo vs custom), case-sensitive collation, or migrations not run.
Common causes
- Connected to the wrong database (default is master)
- Schema prefix missing
- Migrations not applied
- Temp table out of scope
⚡ Quick fix
- Specify the database (Initial Catalog)
- Use schema-qualified names (dbo.Orders)
- Run migrations
Detailed fix by platform
SQL
SELECT DB_NAME(); SELECT * FROM dbo.Orders;
How to diagnose
- Database — Current context?
- Schema — Which schema owns it?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026