Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rkc01
Starting Member
43 Posts |
Posted - 2003-02-20 : 17:08:12
|
| I have a client who wants to rename their NT 4.0 Server running SQL Server 7.0, (don't ask why). I've never had to do this but I picked this up from the KB:...if you have renamed the Windows computer on which you installed SQL Server 7.0. SQL Server 7.0 uses the Windows computer name internally; if you change the Windows computer name, SQL Server detects a different name and generates the error message.NOTE: Your data has not been corrupted or damaged in any way.To resolve this error and start SQL Server again, do either of the following:Run SQL Server 7.0 Setup from the original product CD. Doing so will not reinstall SQL Server or any components; however, it will update SQL Server 7.0 internally to reflect the new Windows computer name. You also need to update SQL Server's internal servername by running the following two stored procedures: sp_dropserver <old_name> go sp_addserver <newname>, local go If SQL Server is configured to listen on either the Multiprotocol or NWLink IPX/SPX network libraries, you'll need to remove them, and then add them back using the SQL Server Network Utility. Has anyone ever done this?Thx,-Rob |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-20 : 17:24:35
|
| We have done it numerous times (a while back though because we are on SQL Server 2000) and it works just fine. |
 |
|
|
rkc01
Starting Member
43 Posts |
Posted - 2003-02-20 : 18:16:12
|
quote: We have done it numerous times (a while back though because we are on SQL Server 2000) and it works just fine.
Thanks for your help. |
 |
|
|
|
|
|