Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
Updating SQL Server’s Internal Server Name
Richard Waymire tells a reader how to avoid passing old server and database names to a new server.
Richard Waymire
November 19, 2001
1 Min Read
Our SQL Server 7.0 server reflects the old server name instead of the current server name. All the databases on the current server, including the master database, are restored from the old server. How can I avoid passing on the old server and database names in the future? If I can't avoid this result, how can I correct it? I found a solution on the Microsoft Web site, but Step A confuses me. Here's the solution:
Step A—Run SQL Server 7.0 Setup from the original product installation CD-ROM. Doing this doesn't reinstall SQL Server or any components; however, it updates SQL Server 7.0 internally to reflect the new Windows computer name.
Step B—Start Query Analyzer, connect to the appropriate SQL Server, then run the following two stored procedures to update SQL Server's internal server name:
sp_dropserver sp_addserver , localwhere oldname is the original computer name and newname is the new computer name.
Do I have to go through the entire installation process when I carry out Step A?
If the MSSQLServer service can't start, you need to follow Step A. However, if SQL Server is running, you can move straight to Step B.
See also, "Upgrading to SQL Server 7" and "Migrating to SQL Server 2008."
About the Author
You May Also Like
.png?width=700&auto=webp&quality=80&disable=upscale)