A simple way to change server name?

[databarn]

Folk,<br>
<br>
I was told to change the name of an NT Server (4.0 w/SP5) that has SQL Server 7.0 installed (a naming conflict arose, and my management lost &lt;grin!&gt. Simple, I thought. But, cannot get SQL Server to recognize new name, and the service won't start. Is there a simple way that I've overlooked to change the name. Or will I have to do a reinstall? I'm concerned ab. damaging to the existing data, and I'm a relative newbie to the admin side of SQL Server.<br>
<br>
Make a good day . . .<br>
. . . barn<br>

 

[jnicho02]

The SQL 7.0 online books says in the FAQ section...<br>
<br>
"I renamed the computer that runs SQL Server. When I restarted SQL Server, I received an error message warning that my installation was corrupted or had been tampered with. What should I do?<br>
<br>
If you change the computer name of the server, you will not be able to start SQL Server until you rerun SQL Server Setup. You will be prompted to upgrade, and the necessary SQL Server options will be reset with the new computer name. After you have upgraded, exit the Setup program. Your databases will not be affected by this procedure."<br>
<br>
.... I hope that you made a backup before making any changes...<br>
<br>
My advice is to try this on a different machine first to check that it works. Tread carefully.<br>

 

[databarn]

nicho02,<br>
<br>
Thanks . . . I think &lt;grin!&gt;. That was what I was hoping _not_ too hear. Found that part in the docs, but was hoping for a less 'extreme' measure. Reason I'm filling in on this job at the moment is that the last admin actually believed ". . . Your databases will not be affected . . ." when he initiated some changes.<br>
<br>
For the moment, I've renamed the server back to its former designation, justified to management by the chance of killing the data. I saw a 'rescue' technique for errant data files somewhere not too long ago, so guess I need to find that again, then rename and reinstall. Sigh-h-h, life was _so_ much simpler with dBase III and Clipper &lt;grin!&gt;<br>
<br>
Make a good day . . .<br>
. . . barn<br>

 

[bigfoot]

No! the documentation you read was not correct. Lookup sp_dropserver and sp_addserver.<br>
I renamed one of my servers successfully this way.<br>
sp_dropserver 'oldservername'<br>
sp_addserver 'newservername'<br>
<br>

 

[databarn]

bigfoot,<br>
<br>
Ah, you may have provided the Brasso for my escutcheon!<br>
<br>
Now, would you perchance know whether this will affect the webs on the server? Or am I going to have to do some bullet-biting? <br>
<br>
(Forget dBase III and Clipper, PC-File is starting to look pretty good. And I think Tim Knopf (Button) still has an active web site!)<br>
<br>
Make a good day . . .<br>
. . . barn<br>

 

[bigfoot]

If you want to convert... I just saw File Maker Pro! Woaaaa.<br>
what a cool product. Just like MS Access, but it works!<br>
<br>
BTW: you will have to change the connect string in your webs if they reference the server name.<br>
Hope this helps

 

[databarn]

Yeah, I've heard that FileMaker grew up. I only knew it when it was the new kid on the block, and wasn't impressed at the time. Now that it's a 'heavy hitter', I haven't the time to go back and play with it again. <br>
<br>
I'm going to implement your fix tomorrow morning. (Actually, it's already implemented, but nobody's online right now.). I know three people who will let me know "immediately, if not sooner" if something goes awry. Since they tend to be seven o'clockers, that'll give me ab. forty-five minutes to recover - and, believe me, I _do_ have a fallback in place! I'm dumb, but I'm not _that_ dumb &lt;grin!&gt;!<br>
<br>
Make a good day . . .<br>
. . . barn<br>
<br>
<br>