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've not read (much) into SQL Server aliasing, it feels like a good, simple way to avoid managing configurations across multiple environments (developing on (local) instance, but production is a DbServerName\Instance), and test environments have different again. To clarify, it's desirable in my opinion to avoid having to change web.config's, spring database xml's manually, or programmatically swapping/changing them on every install.

I don't like lots of manual steps (or overly complex code behind an installer).

Is there any reason why aliasing (local) (a one-off change) to point to a specific server is a bad idea? I can't think of one, but I'm interested to hear the reasoning behind using or not using it...


share|improve this question
up vote 0 down vote accepted

Well, I've done much more reading about this, and it appears this is exactly the use case it was designed for.

share|improve this answer

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.