Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I work in an environment where I have to connect to SQL Server databases hosted on different servers with many different application logins. I might have ten different application logins for a single database instance.

I find it incredibly difficult finding the stored connection parameters in SQL Server's "Connect to Server" prompt. Is it possible to name my various connections with nice aliases (like in SQL Developer or Toad for Oracle) to help me keep track of what connection goes where?

share|improve this question
up vote 1 down vote accepted


That is, you have "App1", "App2" etc to mask the actual DB instance. Then you "train" SSMS to remember logins for that alias.

You set up client-only aliases using SQL Server "SQL Server Configuration Manager", then "SQL Server Native Client Configuration", "Aliases". As per MSDN

share|improve this answer
Perfect! Thanks! – Jordan Parmer Aug 9 '10 at 19:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.