December 14, 2005 at 6:48 am
Hi,
I applied service pack 4 to my two SQL Server 2000 standard edition servers last week.
This week I ran the MS Best Practices Analyser for S2K against the servers and it reported that @@servername returns NULL on one of them, the other server was fine.
The advice on this forum seems to be to use sp_dropserver, sp_addserver and then restart SQL Server to fix this problem, but I can't do this while the system is in use.
Has anyone else had this problem after applying SP4?
Is it a problem if @@servername returns NULL?
David
If it ain't broke, don't fix it...
December 14, 2005 at 9:29 am
If you are definitely sure you don't use @@serverName then it doesn't matter. I would strongly advice that you put it on as soon as possible.
mom
December 15, 2005 at 7:05 am
Didn't have this problem after applying SP4. Are you sure that no renaming of the server has been done ? Because that would do this.
December 15, 2005 at 8:04 am
I am the only person here who manages this server, and I haven't attempted to rename it. The server seems to be running OK , and I don't use @@servername anywhere, so i am going to leave it until the next time I schedule a reboot.
If it ain't broke, don't fix it...
David
If it ain't broke, don't fix it...
December 15, 2005 at 2:53 pm
@@servername is still returning the server name after applying SP4 on my servers.
December 15, 2005 at 4:40 pm
someone had posted once, either bounce the server or create a local instance on the server.
January 25, 2007 at 10:10 am
I had applied sp4 to my sql server 2000 ent ed also, dozens of them, and saw no problem until I tried to update my Litespeed software to 4.6.0.00293 which runs @@servername (the first Litespeed version to do that). That is when I got an error on one server where @@servername returned null. Now, I perfectly understand how to fix it. I want to know what nulled it out. I don't see any blog or article explaining that. What was the cause? I also am the only one managing these sql servers and I haven't made any changes. I was getting the proper servername returned prior to sp4. Anyone know possible cause(s)? It concerns me greatly that something made this change under the covers and I didn't know about it.
January 25, 2007 at 10:22 am
The computername wasn't renamed in the past?
July 4, 2007 at 4:24 am
Hmmm,
thank you, an interesting possibility
That may be possible, as all machines are given a name according to our standard network naming conventions
David
If it ain't broke, don't fix it...
July 4, 2007 at 6:58 am
SQL Server 2000 reaalises the name of the computer dynamically so there is no need to update manually after network name change.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply