1.0.3 MxDB for SQL Server Instance Aliasing

MxDB for SQL Server Instance Aliasing 4

Administrative Tools > Services.) On the snap-in, start the SNS PolyServe

service.

Map Legacy IPs to Virtual IPs

The sns.conf file maps the legacy IP addresses to the new virtual IP

addresses. You will need to add entries for your legacy IP addresses to the

file. The entries must have this format:

<virtual ip> is the IP address assigned to the Virtual SQL Server. For a SQL

Server 2000 instance, <port> is the port number that you specified when

you installed the SQL instance. For a SQL Server 2005 instance, <port> is

port number for TCP/IP Sockets that the SQL Server instance should

listen on. (You specified this number on the Add Virtual SQL Instance

window when you added the SQL instance to the Virtual SQL Server.)

<legacy ip>;<port> is the legacy address to which clients connected before

the consolidation.

Following are some sample entries:

10.10.0.190;3532;10.10.0.190;1433;

10.10.0.150;3533;10.10.0.150;1433;

In both of these entries, the new Virtual SQL Server has the same IP

address as the legacy server.

You do not need to stop the Instance Aliasing service to change the

sns.conf file. The file is dynamic; you can add or remove mappings at any

time. The change takes effect at the next synch interval.

Uninstall Instance Aliasing

You can use Add/Remove Programs to remove the Instance Aliasing

feature. The uninstall removes the NT service, the registry key, and the

sns.template.conf file.