Post reply

Stop SSMS providing the server name

  • August 9, 2017 at 3:34 am

    #332183

    Hello All,

    Can someone please advise if there is a way to stop SSMS providing the server name automatically in the SQL server instance name on connection?

    We want to add an extra level for our users to need to input the server name to verify they are on the correct server before running scripts but i cant see a way to achieve this.

    Kind Regards,

    Tom.

  • August 9, 2017 at 3:47 am

    #1954569

    Tom

    I've never needed to do anything like that.  But I imagine there's a registry key somewhere that determines how many recently used servers to remember in the Connect to Server box.  Edit the registry at your own risk, and always take a backup first.

    John

  • August 9, 2017 at 3:57 am

    #1954570

    I can't think of anything myself, but this sounds more of a training thing that anything. Users should be checking their connection information before running a statement (especially if making DLM/DDL changes). It's not difficult to check, you can see it in the bottom right corner below the query/results pane.

    You can also set up that bar to be a different colour depending on the server. Right click the server connection in the registered servers pane, and select Properties. Go to the Connection Properties tab, and then tick "Use custom color", and select the colour you want. That makes it a lot more visual.

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • August 9, 2017 at 4:00 am

    #1954571

    Thanks guys,

    i agree that this is a training piece, but sometimes we need to try and protect ourselves from user-error!

    Thanks for the time to respond and i will investigate both suggestions.

  • August 9, 2017 at 7:38 am

    #1954625

    In a Server Name drop-down box, move your mousepointer down to the server you want to delete, don't click it, but press Delete button on your keyboard.

    Repeat the same for all the rest servers.

    Close SSMS, because it "memorizes" settings only after you close it.

    Open SSMS again, you will not see these servers.

  • August 9, 2017 at 8:55 am

    #1954652

    Why not make them use different accounts for the different environments?

  • August 10, 2017 at 2:44 am

    #1954744

    We have many people accessing the servers with few admin staff to look after the accounts so duplicating the accounts wouldn't be the ideal solution.

  • August 23, 2017 at 8:51 am

    #1956408

    I could be wrong but I seem to remember it's a good idea to disable the Browser Service, for the very same purpose.  Do your research before you implement that though.

  • August 23, 2017 at 10:14 am

    #1956437

    Ill have a look into this!

  • August 23, 2017 at 11:39 am

    #1956460

    It looks like this question has been asked before, and it looks like you "can" achieve this, but it will require some work and further research. I found the question and proposed answers here: https://stackoverflow.com/questions/1059105/how-to-remove-server-name-items-from-history-of-sql-server-management-studio

    Alan H
    MCSE - Data Management and Analytics
    Senior SQL Server DBA
    Best way to ask a question: http://www.sqlservercentral.com/articles/Best+Practices/61537/

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply