SQL Server Performance Forum – Threads Archive
Renaming Virtual server
Hi all, Is it possible to rename the virtual sql server ? Please forward me the doc/procedure if there is one. Thanks for your help.The official response is to uninstall and then reinstall the virtual SQL server using the new name (Backup existing configuration first). INF: How to Change a Clustered SQL Server Network Name
http://support.microsoft.com/?kbid=307336 Another option is to simply add a new netwrok name resource in the SQL Server cluster group. We have a cluster running like this with 10 names due to a consolidation project. If your DNS is correctly configured the name will be added as soon as you bring it online and other servers on the network can access it. The name resource should be dependent on the SQL IP. /Argyle
Argyle! I have been following your suggesions regarding to Renaming a Virtual SQL Server. I really need your feedback regarding to this issue,how can I get in touch with you on-line I have a Production Virtual (Clustered SQL Server) with an specific Name = SQL01, and I have set up a new machine , same cnfiguration but using SQL03, I have read that the only way to rename the Virtual SQL server is unistalling and installing it again. I generated an entry in the DNS and WINS for SQL01 to point to SQL03, but I do not know if it will not generate future problems. I have testes MSDTC,Full-Text Search, linked-servers, etc, but I have not tested Replication,etc What do you recommend me? I would like to install Virtual (Cluster) SQl Server Name independent of the name the users use in your applications (Connection Strings) so they depend on the name and I am not Can we discuss this, it really will help me to decide what to do Thanks
Just add a network name resource in the new cluster and name it SQL01. Make it dependent on the SQL Server IP in the cluster. Don’t hardcode entires in the DNS and WINS since failover will most likely fail with the error "name already exist" when it tries to bring it online on the second node. At least WINS could cause such issues. Do you really need WINS by the way? Test reaching the virtual servers from different computers before and after failover to test that it works as planned.
]]>