Installing a newer SQL Server Management Studio does not upgrade or replace the Database Engine that a query window uses. SSMS is a client. Run a server-side query in the affected window to identify the exact instance, engine build, edition, and current database.
Last updated: October 11, 2026.
SELECT
SERVERPROPERTY('ServerName') AS ConnectedInstance,
SERVERPROPERTY('ProductVersion') AS ProductVersion,
SERVERPROPERTY('ProductMajorVersion') AS MajorVersion,
SERVERPROPERTY('ProductLevel') AS ProductLevel,
SERVERPROPERTY('Edition') AS Edition,
DB_NAME() AS CurrentDatabase;
GORun this in the same query window that reports the syntax or feature error. Do not rely on the SSMS About dialog: it reports the client version, not the Database Engine that parsed the statement.
Connect to the intended instance explicitly
The Microsoft SERVERPROPERTY documentation defines the instance and product fields returned above. A major version of 16 identifies SQL Server 2022, while 15 identifies SQL Server 2019. Check Microsoft’s build list when you also need the exact cumulative update.
In SSMS, open a new Database Engine connection and enter the correct target. A default local instance can use localhost; a named instance uses a value such as localhostSQL2022. Microsoft’s connection guide also documents explicit TCP host-and-port formats.
Why the old server can still answer
Multiple SQL Server instances can run side by side. Installing a new named instance does not redirect saved connections, registered servers, aliases, application connection strings, or existing SSMS windows. Close the old window only after recording the server name, then connect to the verified new target.
If a named instance is not discoverable, specify its port or verify SQL Server Browser and firewall configuration. Preserve certificate validation when creating the new connection; selecting a different server can expose a certificate-name mismatch that should be fixed rather than bypassed permanently.
Do not uninstall the old instance until databases, logins, jobs, linked servers, and application connections have been intentionally migrated. Continue with version-safe stored procedure deployment, transferring SQL Server logins, and moving Agent jobs.
