{"id":108057,"date":"2025-12-18T15:27:51","date_gmt":"2025-12-18T15:27:51","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/?p=108057"},"modified":"2026-02-19T19:32:21","modified_gmt":"2026-02-19T19:32:21","slug":"common-sql-server-problems-invalid-object-name","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/databases\/sql-server\/common-sql-server-problems-invalid-object-name\/","title":{"rendered":"How to fix the Invalid Object Name error in SQL Server"},"content":{"rendered":"\n

This post is part of a series on common issues encountered in SQL Server<\/a>. This time, we\u2019ll talk about the invalid object name error:<\/p>\n\n\n\n

Msg 208, Level 16, State 1\n\nInvalid object name '{object_name}'.<\/pre><\/div>\n\n\n\n
Causes of the Invalid Object Name error in SQL Server – and how to prevent it<\/h2>\n\n\n\n
Typo<\/h4>\n\n\n\n
The object really could just be spelled wrong \u2013 I couldn\u2019t tell you how many times I had an obvious typo staring me in the face, and was convinced SQL Server<\/a> was wrong. Always use copy & paste or, better yet, rely on IntelliSense<\/a>\/auto-complete \u2013 that\u2019s why they\u2019re there. <\/p>\n\n\n\n
Additionally, products like Redgate’s SQL Prompt feature Intelli-Sense-style auto-complete<\/a> built in to the tool.<\/em><\/p>\n\n\n\n
You could also be using a case or binary-sensitive database or instance. In a case-sensitive database, for example, the following will yield the invalid object name error:<\/p>\n\n\n\n
CREATE TABLE dbo.Users(UserId int);\n\nSELECT UserId FROM dbo.users;<\/pre><\/div>\n\n\n\n
The object doesn’t exist yet<\/h4>\n\n\n\n
Sometimes this error just stems from creating objects in the wrong dependency order. SQL Server allows you to take advantage of deferred name resolution<\/a> with stored procedures; for example:<\/p>\n\n\n\n
CREATE PROCEDURE dbo.ExampleProcedure\n\nAS\n\nSELECT ColumnName FROM dbo.does_not_exist_yet;<\/pre><\/div>\n\n\n\n
SQL Server lets you create the procedure with an invalid reference<\/a>, trusting that you\u2019ll get around to creating the object prior to execution. This will also work with scalar functions<\/a>. You can\u2019t do the same with views<\/a> (or table-valued functions):<\/p>\n\n\n\n
CREATE VIEW dbo.ExampleView\n\nAS\n\nSELECT ColumnName FROM dbo.does_not_exist_yet;<\/pre><\/div>\n\n\n\n
Trying to create this view yields the invalid object name error.<\/p>\n\n\n\n
Wrong object type<\/h4>\n\n\n\n
You may have created a scalar function but are trying to call it like an inline table-valued function<\/a>, or a multi-statement table-valued function if you\u2019re into those for some reason (but generally they should be avoided). The following code returns the invalid object name error message, but I think a more dedicated error would be better:<\/p>\n\n\n\n
CREATE FUNCTION dbo.ExampleScalar() \nRETURNS int\nAS \nBEGIN \n  RETURN (SELECT i = 1); \nEND \nGO \n\nSELECT * FROM dbo.ExampleScalar();<\/pre><\/div>\n\n\n\n
Wrong version\/environment<\/h4>\n\n\n\n
You may have grabbed sample code from somewhere and tried to use it in an older version, where that object simply didn\u2019t exist yet. For example, one of the new internal tables in SQL Server 2025<\/a> is called sys.pause_resume_history<\/code>. If you try to query this table in SQL Server 2022<\/a> or lower, you will get the invalid object name error.<\/p>\n\n\n\n
Or you may have expected \u2013 maybe even really, really wanted \u2013 an object available in Azure SQL Database<\/a> or Azure SQL Managed Instance<\/a> to also be present on-premises. Some examples of this are sys.dm_db_resource_stats<\/code><\/a> and sys.server_resource_stats<\/code><\/a>. If you try to access these views in any on-premises version of SQL Server \u2013 even SQL Server 2025 \u2013 you will get invalid object name.<\/p>\n\n\n\n
The reverse can also be true \u2013 trying to reference a system object in a cloud platform that only exists in on-premises versions.<\/p>\n\n\n\n
Wrong scope<\/h4>\n\n\n\n
It is possible you created a #temp table<\/a> but it\u2019s no longer in scope, because:<\/p>\n\n\n
\n