Manual Browser Alias
SQL does not allow anyone to rename a named instance. Mapping between named and default instances is challenging. Many SQL-centric application, most especially SharePoint, do not support moving to a new server or instance name.
The SQL Browser needs to allow for manual aliasing an existing instance to an arbitrary default or instance name. This way, a DNS redirect can handle the server name resolution and the browser service would transparently look like it connected to the old system. This feature would have a great deal of use in Disaster Recovery, Migrations, Consolidations, and Virtualizations. There are many legacy systems (including SharePoint) where the DBA cannot "fix" a connection string and must make a new system respond to the existing database server and instance name.
Upvotes: 3<=-=Aug 21 2009 3:14PM=-=>
Thank-you for your feedback and request for enhancements to enable some form of virtualization of connections such that the backend server topography can be updated without requiring changes to the client application.
We will investigate ways in which we can address your scenario. Looking at what is currently available, we recommend using aliases that is available on each client machine. Please refer to the following Books Online topic for details on how to create an alias. http://msdn.microsoft.com/en-us/library/ms190445.aspx
Microsoft SQL Server
I am already well aware of the capabilities and limitations of the Client Alias. On larger infrastructures, adding client aliases is prohibitive timewise, especially in a DR situation. This suggestion is a central replacement and supplement for the client alias capabilities.
Client Aliases are not a “fix” for this request.<=-=Nov 13 2015 10:44AM=-=>
Thanks again for reporting the issue. After considering the suggestion against other issues and feature request, we will not be able to address the request at this point. Please let us know if you have further questions.
Young Gah Kim