SQL Server error 7202: Could not find server in sys.servers
A four-part name or OPENQUERY referred to a linked server that isn't defined on this instance, or the name is spelled differently.
- Error number
7202- Severity
- 11
- Category
- Names and objects
What it means
A four-part name such as SERVER1.SalesDb.dbo.Orders, or OPENQUERY(SERVER1, ...), uses a linked server defined in sys.servers. If no linked server has that name, SQL Server raises 7202.
Common causes
- The linked server was never created on this instance, for example after moving a database to a new server.
- The linked server is defined under a different name (an alias, or
SERVER\INSTANCE). - A database name accidentally written as a four-part name, adding an extra prefix.
How to fix it
-
List the linked servers defined here.
SELECT name, product, provider, data_source FROM sys.servers WHERE is_linked = 1;
-
Create the linked server, then set up its login mapping.
EXEC master.dbo.sp_addlinkedserver @server = N'SERVER1', @srvproduct = N'SQL Server'; EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname = N'SERVER1', @useself = N'True';
-
If the object is on this server, use a three-part name instead.
Related errors
More names and objects errors
207Invalid column name4104Multi-part identifier not bound209Ambiguous column name2812Could not find stored procedure2714There is already an object named3701Cannot drop, object not found3702Cannot drop database, currently in use5030Database couldn't be exclusively locked
The code and message text are from the Microsoft Database Engine events and errors reference. Browse the full SQL Server error list or search every database error.
Work on SQL Server in SQLly
A native SQL client for macOS, Windows and Linux with schema-aware IntelliSense, guardrails for risky statements and clear error messages, for SQL Server and the other databases you use.