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

Click OK to return to the Instance Aliasing window. Your mapping entry will be added
to the ia.conf file when you click OK on the Instance Aliasing window.
Modify Instance Aliasing mappings
To change the mapping for a default or named legacy SQL Server instance, select
the appropriate entry on the Instance Aliasing window and then click Edit.
You can then change the mapping as necessary on the Edit Default Alias or Edit
Named Alias dialog. Your changes will be added to the ia.conf file when you
click OK on the Instance Aliasing window.
Delete Instance Aliasing mappings
To remove the mapping for a default or named legacy SQL Server instance, select
the appropriate entry on the Instance Aliasing window and then click Delete.
Recommendations for monitoring Instance Aliasing
We recommend that you create the following device monitor and notifiers to assist
with monitoring Instance Aliasing operations.
• NTSERVICE device monitor. Create the monitor with the default parameters and
add all nodes participating in Instance Aliasing to the monitor. (See “Configure
device monitors” in the HP PolyServe Matrix Server administration guide for more
information about creating the monitor.) This monitor will raise an Alert on the
PolyServe Management Console if the NT Service goes down.
• A notifier triggered by the Alert that is generated by a probe failure of the NTSER-
VICE device monitor. (The Alert is event 4604.) See “Configure Event Notifier
Services” in the HP PolyServe Matrix Server administration guide for more inform-
ation about creating notifiers.
Create a linked server
When creating a linked server to a virtualized SQL Server instance, you must specify
the actual Virtual SQL Instance for the @datasrc parameter. Using an aliased SQL
name (such as an Instance Aliasing name) in the @datasrc is not supported.
For example:
Instance Aliasing126