machine sid & name

What may be the consequence of changing the name and SID of a machine
running a SQL Server 2005?
Thank you.Hello,
After changing the machine name you could drop and create the server with
new name using below system procs...
EXEC sp_dropserver '<old_name>'
go
EXEC sp_addserver '<new_name>', 'local'
go
You need to replace <old_name> above with the old machine name and
<new_name> with the new machine name. After this stop and start the
SQL Server and dependant services.
Are you talking about the Security ID (SID) in sql server side? Can you
please give us more info on that...
Thanks
Hari
"bill tie" <billtie@.discussions.microsoft.com> wrote in message
news:7DDFC773-0F88-4B96-BD93-72C48356C0D9@.microsoft.com...
> What may be the consequence of changing the name and SID of a machine
> running a SQL Server 2005?
> Thank you.
>|||For testing various scenarios (not only SQL Server) I have one image of the
entire system that I simply clone. If you're familiar with virtual machines,
this may ring the bell.
In a network, there are some rules to obey. As a precaution, whenever I
create a new virtual machine, I change its name and security identifier.
This change, however, may have severe consequences, depending on what's
already installed on the machine. I wonder whether such a change may affect
the SQL Server if and when it's pre-installed on the machine.
Suppose the current machine name is "sql2k5sp2". I change the name to
"newSql2k5", and restart the machine. Will your EXECs change the server's
name accordingly? Will the server work aftewards as usual?