Server Fault is a question and answer site for system and network administrators. 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

I have a sql server 2000 of which I want to replicate the data to a sql server 2008. However the output from select @@servername and select serverproperty('servername') on the 2000 server are different and that prevents replication. There is a process to resolve this at . Has anyone done this? What implications are there for following this process? Any 'gotchas' that need to be guarded against? My 2000 server is a lone production server...very scary. Please advise.

share|improve this question
up vote 1 down vote accepted

Easy fix, non invasive. The dropserver/addserver commands really only affect replication, so you will be fine with running them.

Also, this is not renaming the instance, only what it looks like to SQL replication. It sounds like the server had a name change in the past after SQL was installed. That's what causes your queries to return different values.

share|improve this answer
Yes, the original db was named something like databaseTemp, which shows up in @@servername. We use it as something like database (I'm not putting the real name of the instance out of healthy paranoia). I need the @@servername to be as serverproperty('servername'). – peg_leg Jan 31 '11 at 17:26

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.