Accessing Virtual Server Names

Hello,
We are moving from a 2 node, Acitive-Passive cluster to a 4 node cluster; 3
Active 1 passive.
We have 3 Virtual Servers. We have defaulted one virtual server per active
node.
I want to be able to run a different version of our software on each virtual
server; thus three folders one for each for the install. I would like to
update the path variable to point to a different folder based on the virtual
server name.
Can't seem to find out how to get the name of the virtual server the user
logged into.
Or, am I taking the completely wrong approach?
Thanks for any help.
Evan R.
You seem to have your terms and definitions mixed up.
Active-Active-Passive-etc nomenclature is misleading and does not reflect
how clustering in SQL 2000 works.
First, instances are not associated with particular nodes as was the case in
SQL 7.0. The only exception is certain tasks (Service packs, hotfixes, disk
changes) must be done from the node currently hosting the virtual server.
You can have sixteen instances per cluster, regardless of the number of host
nodes in the cluster. SQL 2000 supports up to 4 nodes per cluster. You can
have only one default instance per cluster. I suggest using only named
instances on a cluster for consistancy. Since each instance appears as a
separate server on the network, a query of the @.@.servername global variable
will easily distinguish which server a user is connected to.
Geoff N. Hiten
Microsoft SQL Server MVP
"BeenThereGotLost" <BeenThereGotLost@.discussions.microsoft.com> wrote in
message news:54DDC256-9949-421F-8240-82C54A882B1C@.microsoft.com...
> Hello,
> We are moving from a 2 node, Acitive-Passive cluster to a 4 node cluster;
> 3
> Active 1 passive.
> We have 3 Virtual Servers. We have defaulted one virtual server per active
> node.
> I want to be able to run a different version of our software on each
> virtual
> server; thus three folders one for each for the install. I would like to
> update the path variable to point to a different folder based on the
> virtual
> server name.
> Can't seem to find out how to get the name of the virtual server the user
> logged into.
> Or, am I taking the completely wrong approach?
> Thanks for any help.
> Evan R.
|||Thanks Geoff. Hopefully this will clear up my question.
We stage equipment & databases for our customers. The customer's database
replicates to a database on a named SQL instance running on a virtual server
in the cluster.
To stage the equipment our manufacturing folks have to log into the virtual
server and run some command line utilities. The utilities build the
replication, accounts, etc. I would like to modify the path in the
environment based on the name of the virtual server. This would allow me to
have different versions of the software for different virtual servers. I am
constraining the problem by putting only one instance of SQL on each virtual
server.
From a cmd shell, I need the name of the virtual server the manufacturing
person has logged into. I'm willing to use command line utility, Script, or
API to access the virtual server name.
"Geoff N. Hiten" wrote:

> You seem to have your terms and definitions mixed up.
> Active-Active-Passive-etc nomenclature is misleading and does not reflect
> how clustering in SQL 2000 works.
> First, instances are not associated with particular nodes as was the case in
> SQL 7.0. The only exception is certain tasks (Service packs, hotfixes, disk
> changes) must be done from the node currently hosting the virtual server.
> You can have sixteen instances per cluster, regardless of the number of host
> nodes in the cluster. SQL 2000 supports up to 4 nodes per cluster. You can
> have only one default instance per cluster. I suggest using only named
> instances on a cluster for consistancy. Since each instance appears as a
> separate server on the network, a query of the @.@.servername global variable
> will easily distinguish which server a user is connected to.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> "BeenThereGotLost" <BeenThereGotLost@.discussions.microsoft.com> wrote in
> message news:54DDC256-9949-421F-8240-82C54A882B1C@.microsoft.com...
>
>