Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

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

Took the job of monitoring and tuning a few dozens SQL Server 2012 Enterprise Ed. SP1 (64 bit) on Windows Server 2008 R2 Standard Ed. running inside virtual machines.

All of them on running

select @@servername
select * from sys.servers 

return the same machine autogenerated during Windows setup name WIN-MIQD9ME78FK.

SQL Server name

These production servers works over 2 (probably much more) years.

As far as I can guess the hosts' name were changed after installing SQL Server.

What are the compelling reasons for updating SQL Servers name for its real host names?

And which surprises should I be ready for after such changes?

share|improve this question
up vote 3 down vote accepted

If you aren't using SQL Server Replication or remote jobs (MSX Jobs) then it really doesn't matter all that much. It's a bit annoying when the server names don't match when you run select @@servername, but it's really not that big a deal for the most part.

share|improve this answer
It's also very easy and, unless the old server name is hard-coded somewhere, harmless to fix. – Aaron Bertrand Jan 13 '14 at 15:20
The main problem is in down-time since, it requires restarting the instances and the fear of unforeseen consequences – Gennady Vanin Геннадий Ванин Jan 14 '14 at 6:50
If there's a problem after changing it, just change it back and restart the service again. – mrdenny Jan 14 '14 at 6:54

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.