HP PolyServe Software for Microsoft SQL Server best practices for instance aliasing and connectivity white paper

Short Description
HP has created a series of white papers that provide IT professionals with best practices related to implementing HP PolyServe Software for Microsoft® SQL Server, version 3.6. These documents assist solution architects, SQL database administrators, storage administrators, service administrators, and IT technical management personnel as they develop their consolidation/virtualization platform standard, architecture blueprint, and deployment strategy for Microsoft SQL Server.

Website: h71028.www7.hp.com | Filesize: 369kb
No of Page(s): 6

Content
Q: How does the instance aliasing tool solve my problem with stacking multiple default instances or same-named instances on a single server?
A: The HP PolyServe Software instance aliasing (IA) tool solves a consolidation problem that commonly occurs with Microsoft SQL Server—how do you stack multiple default instances or same-named instances on a single server? To consolidate Microsoft SQL Server using HP PolyServe Software, you must stack instances. However, default instances or same-named instances cannot coexist on a single server because of the name collision. Therefore, stacking requires converting default instances to named instances and same-named instances to unique names. Normally, this action requires changing the client connection strings to reflect the instance naming changes.
The HP PolyServe Software IA technology solves this problem by providing a method where:
• Client connection strings do not have to be changed, and
• Client connections are redirected to the new-named instances.
The IA tool allows you to assign uniquely-named instance aliases to multiple default instances, enabling stacking without having to change the client connection strings. The client continues connecting to the legacy IP address with its existing client connect string. The IA tool redirects the client to the new uniquely-named instance according to the defined IA mapping. This action is transparent to the client, users, and IT technical management personnel.
…
HP recommends using the IA tool when:
• The client legacy IP addresses are hard-coded and for either practical reasons or company policy, you are unable to change the application’s connect string.
• You need to stack multiple default instances and/or instances with the same name.
• There are potentially thousands of clients needing modifications, making application connect strings change expensive and problematic.
• Applications may have several locations for the client connection strings and/or the locations of the connection strings are unknown and you do not want to perform the discovery and application level testing to ensure that all of the connection strings have been corrected.
• You want to access:
– The same SQL instance as both a named instance and a default instance at the same time.
– The same instance by two or more default instance names at the same time.
…