4.1.0 HP PolyServe Software for Microsoft SQL Server administration guide (T5392-96074, October 2010)

8 Instance Aliasing
The Instance Aliasing feature can be used to map your existing legacy SQL
connections to the Virtual SQL Server connections used with HP PolyServe Software.
SQL clients can then continue to use the legacy connection string to access the SQL
database in its new location.
Overview
The mappings from legacy SQL connections to the new Virtual SQL Server connections
are created via the PolyServe Management Console and then stored in the Instance
Aliasing mapping file, ia.conf.
When clients connect via the legacy SQL connections, the mapping information is
used to connect the clients to the Virtual SQL Server providing the appropriate virtual
SQL instance.
HP PolyServe Software provides a PolyServe SQL Browser Service that can perform
the mapping operations for both default and named virtual SQL Server instances,
and can also handle connections for SQL Server instances that have not been
virtualized. This service must be enabled if you will be mapping named instances.
When the PolyServe SQL Browser Service is enabled, it is used instead of the Microsoft
SQL Browser Service, which cannot handle mappings for virtual named instances or
name-to-name redirection. If you are mapping only default SQL Server instances,
enabling the PolyServe SQL Browser Service is optional.
Instance Aliasing port considerations
Legacy SQL mappings require the legacy port to be unused by other SQL Server
instances. If a port conflict does exist, Instance Aliasing will detect the conflict and
remove the legacy SQL mapping from that port. On each node, the port assigned
to a legacy mapping cannot also be used by any real instance, named or default,
installed on that node.
HP PolyServe Software for Microsoft SQL Server 4.1 administration guide 121