Bajal,

Hope the following information helps:

* To handle jobs, script out all of the jobs and then delete them
-rename the server back to the original name if already changed. Rename the
server to the new name-SQL Server 2000 and above only.
* Sp_dropserver <old_name>
* Sp_addserver <new_name>, 'local'
* Restart the SQL Server service for the change to @@SERVERNAME to
take effect.
* Copy local or remote packages if needed. Be sure to check on
connections to ensure that it is pointing to the new server.
* Add back the jobs by running the script generated from the first
step-SQL Server 2000 and above only.

Note: SQL Server 7.0 stores in the msdb..sysjobs table, the file
originating_server value to '(local)' referencing the local server.
Therefore, no matter how the server name is modified, the change does not
affect the local server jobs. SQL Server 2000 on the other hand supports
multi-instances, the originating_server field contains the instance name in
the format 'server\instance'. Even for the default instance of the server,
the actual servername is used instead of '(local)'. Therefore, after the
Windows server is renamed, these jobs still reference the original server
name and may not be updated or deleted by the process from the new server
name.

Sang Nahm
-----Original Message-----
From: Bajal Mohamed [mailto:[Email Address Removed] Wednesday, September 18, 2002 1:49 AM
To: LazyDBA.com Discussion
Subject: Renaming Windows Server ....


Hi,

We have sql2k running on Win'2000 server. Now we want
to rename the windows server.

Will the SQL Server run perfectly after renaming
windows server?

Do I have to take any proactive steps?


Tnx
Bajal

=====
Best Regards,
Bajal

__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page