3.6.0 MxDB for SQL Server Installation and Administration Guide (5697-7088, December 2007)

Chapter 6: Instance Aliasing 91

Sql Browser connection string. Specify the names of the legacy server

and the legacy instance. Then select the SQL Server version that applies to

the legacy instance.

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 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 NTSERVICE device monitor. (The Alert is event 4604.) See

“Configure Event Notifier Services” in the PolyServe Matrix Server

Administration Guide for more information about creating notifiers.