1. Sql Server Rename Username

It is possible to rename the named instance of SQL server 2K, first use spdropserver and spaddserver (drop the old server name and add new server name in sysservers table). Turn down the instance and create the same folder structure as the old installation folder for this renamed instance, both for installation folders and data folder appropriately i.e $OldInstanceName to $NewName, also search and replace this old instance name in registery.then run the 'rebuildm' utility for rebuilding the system databases now reboot the system and make sure SQL server is running under new name. Then detach and attache the user databases to the new location (new folder i.e $NewName). The spdropserver / spaddserver method works only for the DEFAULT instance though.

Ahh, I see, so your point is that it's a login to sql server that is called a 'windows login' because it's associated with a windows domain account. However thats not what that link you've just provided says, under the section 'SQL Server-level principal' it has the name 'SQL Server Login'. – BenCr Mar 23 '11 at 13:07. # Rename with a GUI - SQL Server Management Studio. Connect with SQL Server Management Studio. Make sure Object Explorer pane is open. Click on the database name (as the rename option from the dropdown will be greyed out) and type in the new name. The Azure Portal should show the reflected the change almost immediately.

On the default instance only, by using spdropserver / spaddserver you can change the server name reported by @@SERVERNAME. You would also have to change your machnine name if you wanted remote clients to be able to connect to that instance using that name.For a NAMED (non-default) instance it isn't so easy.

The supported method is to uninstall / re-install. There are registry hacks to rename a default instance, but you may prefer the safer option of re-installing:.

Sql Server Rename Username

Old post, but new day.We have an existing named instance of SQL Express. We want to replace it with a full named SQL instance in such a way that it does not affect the application side of the server.

Our thought was to install a second named instance, copy the databases from the Express version to the full version, remove (or rename)the Old Express named instance, then use spdropserver and spaddserver process to change the full version SQL named instance to the old express named instance, Stop and restart services. Would that work?The point may be moot as we are probably going to try it and see if it does work. This is with SQL 2012, by the way.