Rename a Computer that is running MS SQL Server 2005

Hi everyone,
Here's what we want to achieve:
We have a production computer hosting a default instance of MS SQL
Server 2005 (Let's use the name DBSVRA)
We have another computer that is currently has a default instance of
MS SQL Server 2005 (DBSVRB)
Because DBSVRB is much faster, efficient, etc..., we want to move all
the databases from DBSVRA to DBSVRB
Now, we don't want to adjust our connection strings from our
applications, we want to simply
rename DBSVRB to DBSVRA.
I checked the following article:
http://msdn2.microsoft.com/en-us/library/ms143799.aspx and all the
criterias under "Before you begin" section is met.
a) We don't have a failover cluster --> can happen in the future
b) We don't have replication set-up --> can happen in the future
c) We are not using reporting services --> can happen in the future
d) No data mirroring --> can happen in the future
Anyway, after all of this, I just find that this might have adverse
effects by simply renaming a computer. For one, we have just tested
this scenario and while the rename of the server was successful and I
was able to log to MGMT Studio using the new name successfully.
However, I have noticed that under Security->Logins, the
<INSTANCENAME>\SQLServer2005MSFTEUser$<INTSANCENAME>
$MSSQLSERVER,<INSTANCENAME>\SQLServer2005MSSQLUser$<INSTANCENAME>
$MSSQLSERVER, <INSTANCENAME>\SQLServer2005SQLAgentUser$<INSTANCENAME>
$MSSQLSERVER
still have the <INSTANCENAME> of the old server name. Is this an
issue?
I don't know...while it's doable, I just don't feel comfortable about
this. What are your thoughts?Did you get any responses to this? I have the same concerns!!!
"audrey.nsh@.gmail.com" wrote:
> Hi everyone,
> Here's what we want to achieve:
> We have a production computer hosting a default instance of MS SQL
> Server 2005 (Let's use the name DBSVRA)
> We have another computer that is currently has a default instance of
> MS SQL Server 2005 (DBSVRB)
> Because DBSVRB is much faster, efficient, etc..., we want to move all
> the databases from DBSVRA to DBSVRB
> Now, we don't want to adjust our connection strings from our
> applications, we want to simply
> rename DBSVRB to DBSVRA.
> I checked the following article:
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx and all the
> criterias under "Before you begin" section is met.
> a) We don't have a failover cluster --> can happen in the future
> b) We don't have replication set-up --> can happen in the future
> c) We are not using reporting services --> can happen in the future
> d) No data mirroring --> can happen in the future
>
> Anyway, after all of this, I just find that this might have adverse
> effects by simply renaming a computer. For one, we have just tested
> this scenario and while the rename of the server was successful and I
> was able to log to MGMT Studio using the new name successfully.
> However, I have noticed that under Security->Logins, the
> <INSTANCENAME>\SQLServer2005MSFTEUser$<INTSANCENAME>
> $MSSQLSERVER,<INSTANCENAME>\SQLServer2005MSSQLUser$<INSTANCENAME>
> $MSSQLSERVER, <INSTANCENAME>\SQLServer2005SQLAgentUser$<INSTANCENAME>
> $MSSQLSERVER
> still have the <INSTANCENAME> of the old server name. Is this an
> issue?
> I don't know...while it's doable, I just don't feel comfortable about
> this. What are your thoughts?
>
>