Vista - Move VHD - SQL Instance Name Changes

I have a test environment setup under VS 2005 R2. The VM is running Windows
Server 2003 with SQL Server 2005. I copied the VHD over to another physical
box, but when I bring it up, the SQL Server instance name is different.

In the original VM on the original host system, the SQL instance name is
something like "ABC-XYZ", and the computer name is "JSELK46". I then copy
the VHD over to the new host machine, create a new VM in VS, using the copy
of the VHD. When I bring it up, one of my apps that access SQL errors out,
since it can't find that SQL instance. I just discovered that the SQL
instance name is now "JSELK46", which is the VM's computer name. All of the
databases and tables are intact, but the instance name was lost.

Any idea how/why this happens? Its a real pain to have to go change all
references to the SQL instance name.

Thanks

Does anyone have any ideas about this?

"John Schneider" wrote:

On Tue, 16 Dec 2008 07:23:01 -0800, John Schneider
<johnmsch@xxxxxx> wrote:
This is better asked in an sql-server oriented newsgroup.
What sqlserver does when restored to a different computer is probably
what they can discuss there.

--

Bo Berglund (Sweden)

"Bo Berglund" wrote:
Thanks for the reply Bo, but I've posted there also and still no replies.

BTW, just as a point of clarification, SQL Server is not being restored to a
different computer. Since the VHD file is just being moved from one host to
another, the actual "computer" (the Virtual Machine) is still exactly the
same. That's what is driving me crazy!

On Tue, 16 Dec 2008 13:08:02 -0800, John Schneider
<johnmsch@xxxxxx> wrote:
When you say you copied the VHD file over to another computer and used
it there you created a new virtual machine on that other PC and
pointed it to the VHD file (copied). This will in actual fact make one
very significant change to the SQL server PC, it changes the network
card MAC address. And this is a significant change to the SQL Server I
am used to (SQLServer 2000) at least.
To me this counts as the PC being *restored* to another PC.
SQLServer is known to do strange stuff if it is restored like this....

--

Bo Berglund (Sweden)