February 2, 2011 at 6:00 pm
1) sp_dropserver 'OldServerName'
2) sp_addserver 'NewServerName', local
3) then Retstart mssql
this is useful for linked server.
----------
Ashish
February 2, 2011 at 6:05 pm
crazy4sql (1/31/2011)
its as simple as this.....as you cant rename the system database, similarly you cant rename the servername
This is what you said in a previous post. Were you referring to something else?
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
February 2, 2011 at 6:19 pm
My question would be why do you care about the company name in the documentation? It's not tied to a license, and no one would see it. SSMS != SQL Server, and I'm not sure why you think this is an issue.
February 2, 2011 at 6:22 pm
Michael L John (2/2/2011)
crazy4sql (1/31/2011)
its as simple as this.....as you cant rename the system database, similarly you cant rename the servernameThis is what you said in a previous post. Were you referring to something else?
Dont tell me you dont know the difference between linked server and real server.
The query suggest above is useful for renaming linked server.
But whatever the case, As steve suggested follow that and close this topic.
----------
Ashish
February 3, 2011 at 3:21 am
crazy4sql, if you look in BOL at the topic How to: Rename a Stand-Alone Instance of SQL Server 2005, you'll see that
sp_dropserver <old_name>
GO
sp_addserver <new_name>, local
GO
is exactly how to do it. As I have many times.
February 3, 2011 at 4:20 am
sp_dropserver <old_name>
GO
sp_addserver <new_name>, local
GO
is exactly how to do it. As I have many times.
Agree cath, but it will not remove the original name of the server which you will get by 'Select @@servername'.
This is just for linked server. You can rename your server by your query to other name in linked server.
For confirmation, Go to SSMS--ServerObjects--LinkedServers.... and then try your queries.
you will see names are getting modified/added there.
----------
Ashish
February 3, 2011 at 7:28 am
Just to make sure I am not insane, I took one of our dev boxes, renamed the MACHINE from Dev001 to Dev010, re-added it to Active Directory, and used sp_dropserver /sp_addserver.
When I run SELECT @@SERVERNAME, it returns "DEV010".
I just did this on 4 machines last week when moving them from dev to production. This is a typical scenario that I have encountered many times.
For example, a new server is purchased as a replacement. Let's call them OldServer and NewServer.
NewServer is configured, updated, patched and all the other things that you need to do in this situation.
Once the change over is scheduled to occur, we backup the DB's from OldServer and move them to a common storage location.
At this point, OldServer gets physically shut down.
NewServer is brought on-line, the MACHINE is renamed to OldServer, and aded to Active Directory.
SQL Server is renamed, the databases are restored, and everything works perfectly.
Maybe in SQL 6.0/6.5 would a rename require a reinstall, but this has been available since 7.0
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
February 3, 2011 at 8:19 am
crazy4sql, I don't want to appear rude, but you're wrong. My experience of renaming local instances using those procs is the same as Michael's. To quote the BOL entry I mentioned in my last post:
To verify that the renaming operation has completed successfully
Select information from either @@servername or sys.servers. The @@servername function will return the new name, and the sys.servers table will show the new name.
And that's exactly what happens, sweet as a nut.
February 3, 2011 at 10:32 am
Changing the instance name works fine, as the last two posters have noted, but this thread was about changing the "Company Name" on the installation. That I am not sure of where it's stored, or even surfaced for SQL Server.
February 3, 2011 at 11:38 am
I looked in the registry, and in almost every file I could think of on the drives, and under the rock in my backyard. I couldn't find it.
I installed SQL 2005 on a spare machine, express, developer, standard, and enterprise. The question didn't appear.
I went to help, about in SSMS. Nothing.
Are we sure the original poster isn't talking about Office? 😛
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
February 3, 2011 at 2:14 pm
Nope, I'm about to start a new install of 2005 and see if I see it. Don't remember the "name/company" thing in the R2 install I did
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply