Change @@servername in SQL 2005

Question

Change @@servername in SQL 2005

Viewing 11 posts - 1 through 12 (of 12 total)

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

The_SQL_DBA SSChampion Points: 10494 More actions · Answer 1

You can do so by changing the name of your server from windows OS. Then restart SQL server. Your new name should reflect when you run select @@servername again.

Thanks!!

The_SQL_DBA
MCTS

"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."

Erin. SSCertifiable Points: 5237 More actions · Answer 2

The OS recognizes the development server name correctly. It seems like everything recognizes it correctly except @@servername.

The_SQL_DBA SSChampion Points: 10494 More actions · Answer 3

You would need to do this then, won't affect anything else unless you have any jobs that use the old server name. If so you need to updated them with the new server name.

1. sp_dropserver 'old_name'

2. go

3. sp_addserver 'new_name','local'

4. go

Also restart sql server as

net stop mssqlserver

net start mssqlserver

This should do the trick for you

Thanks!!

The_SQL_DBA
MCTS

"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."

Erin. SSCertifiable Points: 5237 More actions · Answer 4

I also noticed the following logins:

PRODUCTION\SQLServer2005MSFTEUser$PRODUCTION$MSSQLSERVER

PRODUCTION\SQLServer2005MSSQLUser$PRODUCTION$MSSQLSERVER

PRODUCTION\SQLServer2005SQLAgentUser$PRODUCTION$MSSQLSERVER

They should be:

DEVELOPMENT\SQLServer2005MSFTEUser$DEVELOPMENT$MSSQLSERVER

DEVELOPMENT\SQLServer2005MSSQLUser$DEVELOPMENT$MSSQLSERVER

DEVELOPMENT\SQLServer2005SQLAgentUser$DEVELOPMENT$MSSQLSERVER

Would below script fix these as well?

exec sp_dropserver PRODUCTION

GO

exec sp_addserver DEVELOPMENT, 'local'

GO

The_SQL_DBA SSChampion Points: 10494 More actions · Answer 5

Did you say you restored the dev server system databases with the backup from production system databases?

Thanks!!

The_SQL_DBA
MCTS

"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."

Erin. SSCertifiable Points: 5237 More actions · Answer 6

Erin.

SSCertifiable

Points: 5237

February 19, 2009 at 8:30 am

#946760

Yes.

Richard M. SSCertifiable Points: 7401 More actions · Answer 7

um....

sp_dropserver will "remove a server from the list of known remote and linked servers on the local instance of SQL Server"..... so it will not affect at all your running instance.

when you run sp_helpserver you are getting production right?

Not sure if only the sp_addserver with the 'local' option will do the trick

_______________________________________________________________________
For better assistance in answering your questions, click here[/url]

The_SQL_DBA SSChampion Points: 10494 More actions · Answer 8

I dont think you need to restore system databases to make a copy of production. Because Dev and Prod are completely different instances.

Dev and prod need to match with their schema and not system databases.

To avoid any other problems please revert back your dev system databases from backup. Like if you are updating something on Dev box with the criteria of @@servername then it would update your production(only if this job uses an account that exists on prod, but it is a possibility)

Thanks!!

The_SQL_DBA
MCTS

"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."

Richard M. SSCertifiable Points: 7401 More actions · Answer 9

Well, found this http://blogs.techrepublic.com.com/datacenter/?p=192

So apparently the trick with sp_dropserver/addserver and restarting the SQL services does accomplish what you need?

_______________________________________________________________________
For better assistance in answering your questions, click here[/url]

ps. One Orange Chip Points: 29423 More actions · Answer 10

Richard M (2/19/2009)
um....
sp_dropserver will "remove a server from the list of known remote and linked servers on the local instance of SQL Server"..... so it will not affect at all your running instance.
when you run sp_helpserver you are getting production right?
Not sure if only the sp_addserver with the 'local' option will do the trick

You can change the Servername using sp_addserver.

Refer http://msdn.microsoft.com/en-us/library/ms143799.aspx?ppud=4

Pradeep Singh

Richard M. SSCertifiable Points: 7401 More actions · Answer 11

yup... realized that... see my previous post...

_______________________________________________________________________
For better assistance in answering your questions, click here[/url]