• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3073
  • Last Modified:

Change computer name

I'm running NT 4.0 and SQL Server 7.0.  I need to change the name of the computer.  When I do & reboot SQL Server will not start.  I tried sp_addserver, sp_dropserver, & sp_setnetname before changing the computer name but I must be missing something as it does not work.  It seems like what ever I do must be done before I change the name as once I do I can not start SQL Server.  Sort of a Catch 22.
0
Argonaut
Asked:
Argonaut
1 Solution
 
UncleMattCommented:
As far as I know you can't change the computer name of a SQL server without re-installing it.

It's all in the books online somewhere.

Matt.
0
 
nigelrivettCommented:
change the name
reboot - sql server will fail to start
rerun the sql server setup - installshield will say that it is upgrading the system. It will actually change all the registry entries.
Reboot the server again and everything shou be OK.
You may have to add the server name which you already know how to do.
0
 
chigrikCommented:
Read about "How do I change the name of SQL Server?"
http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14155

It's there from:

"
With SQL 7.0 you will need to re-run setup to reset the server name. Setup will detect the name conflict, resolve it, and then finish.
"

Hope this helps
0
 
ArgonautAuthor Commented:
Thanks,

I had some problems with the CD.  It would not accept the Enterprise CD, had to use Standard CD.  I though it was Enterprise to begin with.  I know Enterprise need Win 2000 Advanced but I'm running NT 4.  Do you know what is up here?

Any way after running setup the server would start but @@SERVERNAME still returned the old name.  So I ran:

sp_dropserver <oldname>
go
sp_addserver <newname>, local

After a re-start the name was completely changed.
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now