First collect the output of the current instance configuration. You can get the instance name stored in the SQL Server metadata.
Make sure you have backup of all the database if you are changing the production server instance name.
<br /> sp_helpserver<br /> select @@servername<br />
You can change the instance name using below query.
Default Instance
<br />
sp_dropserver 'old_name'<br />
go<br />
sp_addserver 'new_name','local'<br />
go<br />
Named Instance
<br />
sp_dropserver 'Server Name\old_Instance_name'<br />
go<br />
sp_addserver 'ServerName\New Instance Name','local'<br />
go<br />
Verify sql server instance configuration by running below queries
<br /> sp_helpserver<br /> select @@servername<br />
Restart the SQL Server Services.
<br /> net stop MSSQLServer<br /> net start MSSQLServer<br />
Renaming instances in the AI era
The procedure above still works — sp_dropserver and sp_addserver haven’t changed. Where this comes up in 2026 is consolidation: before a cloud migration or a container rollout, teams rename and merge instances so connection strings and automation stay sane. Get the naming right once, because every pipeline, agent, and dashboard downstream will hardcode it. If you’re heading down that modernization path, start here: Legacy to Cloud-Native: A Database Modernization Playbook
