Deleting Old server names from "Connect to Server" dialog in SSMS

In an earlier Denali CTP, we had introduced a mechanism for customers to delete the un-used/not required server names from the drop down in connection box in SSMS. There has been a big customer ask for helping them remove the redundant server names from the MRU list.

Here is a blog post from Devesh Nagpal, a developer in the SQL Server Manageability Team describing this new feature in SQL Server Code Named “Denali” CTP3.


There are a few undocumented ways on doing this as mentioned here,

The problem with using undocumented feature were

1) There were side effects of doing it like losing SSMS specific Tools | Options settings, OE Details List View Customizations, the MRU list for OE Details Search, and MRU for Reports.

2) There was no official support from Microsoft.

We will now be supporting Deleting the server name from MRU list officially. This will help customers remove any Server name from the drop down list they do not wish to see. With regard to addition of servers to this list, there is no change to the earlier behavior – the server name will get appended to the list once you connect to it.

Here is a simple demonstration of how you can now easily remove the Server names from MRU list from CTP2 Denali.

As shown in the picture below there might be multiple machines you have connected to in SSMS. All will be shown in history sorted by when you have last used them.


To delete the dead servers from the list, select the name you want to delete either via mouse or via keyboard. As shown in the image below.


Now press the delete key on the keyboard, the item will be deleted from the list.You can delete as many items as you want. Note that the text in the box will remain to your last selection even after delete.


Current Limitations

1) No multiple select and delete, the delete has to be one by one for server names. There is no multiple select and delete option.

2) You will have to rely on keyboard for actually deleting the item, right click on item and then deleting it is not supported.

3) There is no global list to keep track of the server names users have deleted and not to add them in the list again. The list will be re-populated once the user connects to a new server name (which is not present in the list).

Devesh Nagpal can be reached at

Comments (15)
  1. Aaron Bertrand says:

    What would be really great is if we could have access to the list. The issue many users have is they have *duplicate* entries, not simply too many. It's not necessarily true that any of the servers in the list are dead, but one may be Windows auth, one may be sa, one may be a peon SQL auth user, etc. I'm thankful for the usability enhancement but I think it could be so much more powerful if we could really tell which entry was which.

  2. Scott M. says:

    I just tried this using SSMS 10.0.1064.0 and it didn't work.

  3. Deleting the old server name in sql server2005 says:

    delete the file in the following location C:Documents and Settings<user>Application DataMicrosoftMicrosoft SQL Server90ToolsShellSEMmur.dat

  4. Larry H. says:

    This does not work on SS2008R2 RTM.  Not being able to clear selected items from this list is a serious annoyance!  Wake up Microsoft.  This is something that affects EVERY user of SSMS!  Why would you want to annoy the vast majority of your SSMS users?

  5. M says:

    It should also work for logins dropdown (e.g. 3 logins for same server and I need to delete 2 of them)

  6. RobIII says:

    Still doesn't work (Microsoft SQL Server Management Studio 11.0.3000.0 here).

  7. Gabor says:

    It works with Microsoft SQL Server Management Studio 11.0.3128.0. Thank you.

  8. Michael O. says:

    Quasi worked on SSMS 10.0.5512.0 (2008), it ended up deleting ALL the entries in the drop down list.

  9. p Rehm says:

    This does not work in

    Microsoft SQL Server Management Studio 11.0.2100.60

  10. fel0nious says:

    Like Gabor above, I have version 11.0.3128.0, however this does not work: it simply deletes the selected text in the combo box leaving the item in the dropdown. However, the connect to dialog has been acting funny for me in different ways also: The last-connected-with user is not the one that is selected either, and remembered passwords are frequently lost.

  11. ANair says:

    Thanks! it works on SSMS 2012 v 11.0.2100.60

  12. Shailp says:

    It worked for me in SQL Server Management Studio 2012.

  13. Martin says:

    Please help.  I have an application that connects to a SQL Server db via a DSNLESS connection string using the ODBC driver. I have implemented it at several sites already without any problem.   I'm currently deploying it to another new site.  However, the app is failing to connect first time but it's bringing up a MS SQL login screen where it displays the server, user id and password fields populated with the correct connection details.  If I click OK on this screen without changing anything it then connects.  On checking on the server drop list I saw that there are 2 instance names which are exactly the same.  They both look like SERVERSERVERSTORE.  

    I confirmed this by setting up an SQL Server odbc data source on the same server which is installed with MS SQL  Server 2012.  I went into MS Studio Management and deleted one instance but it still comes up as discussed up.

    I want to know how to delete 1 of the instances so it doesn;t come up and interfere with my application.

  14. akpan michael says:

    it worked perfectly well in Microsoft sql server 2012!

  15. Mark says:


    Because that does not happen at all

    Those who are saying it does work are clearly deluded and have not correctly tested

Comments are closed.

Skip to main content