about another instance of virtual server on sql2000 cluster

Hi,
i have a cluster a/p windows 2000 & SQL2000 , now i would like install
another virtual sever SQL on passive node for make this cluster
active/active.
The question is :
When i start a SQL wizard for add a new virtual server when installation
wizard aask me a path for sql binary i must use the same exist path use for
the virtual sql server installed or i must choice another path for ex.
c:\....\SQL\Virtual2 ?!?!?
Thanks.
--
No matter whether it's clustered or not, each SQL2000 instance has its own
location for its binaries (well some binaries for the tools are shared). You
can specify the same path, and the install will create a different folder
under that path for each instance. For instance, if you specify D:\MyDir for
the binaries (program files), the install will place the binaries under
D:\MyDir\MSSQL for the default instance, and under
D:\MyDir\MSSQL$<InstanceName> for a named instance.
Check out the section titled "File Paths for SQL Server 2000" in BOL.
Also, technically you don't really install another virtual server on the
passive node. Rather, you install another virtual server in the cluster, and
when you install it, the binaries are placed on all the nodes. You can
configure the virtual server to run on a particular node in its normal
operating mode.
Linchi
<io.com> wrote in message news:%23c$txrdzFHA.460@.TK2MSFTNGP15.phx.gbl...
> Hi,
> i have a cluster a/p windows 2000 & SQL2000 , now i would like install
> another virtual sever SQL on passive node for make this cluster
> active/active.
> The question is :
> When i start a SQL wizard for add a new virtual server when installation
> wizard aask me a path for sql binary i must use the same exist path use
> for the virtual sql server installed or i must choice another path for ex.
> c:\....\SQL\Virtual2 ?!?!?
> Thanks.
>
> --
> --
>
|||Thanks you!
"Linchi Shea" <linchi_shea@.NOSPAM.ml.om> wrote in message
news:ex9%23QsezFHA.3924@.TK2MSFTNGP14.phx.gbl...
> No matter whether it's clustered or not, each SQL2000 instance has its own
> location for its binaries (well some binaries for the tools are shared).
> You can specify the same path, and the install will create a different
> folder under that path for each instance. For instance, if you specify
> D:\MyDir for the binaries (program files), the install will place the
> binaries under D:\MyDir\MSSQL for the default instance, and under
> D:\MyDir\MSSQL$<InstanceName> for a named instance.
> Check out the section titled "File Paths for SQL Server 2000" in BOL.
> Also, technically you don't really install another virtual server on the
> passive node. Rather, you install another virtual server in the cluster,
> and when you install it, the binaries are placed on all the nodes. You can
> configure the virtual server to run on a particular node in its normal
> operating mode.
> Linchi
> <io.com> wrote in message news:%23c$txrdzFHA.460@.TK2MSFTNGP15.phx.gbl...
>
|||Sorry , a lat question :
i have isntalled the new virtual server and it work fine but i see that the
new instance of sql virtual server is myclustersql02\myclustersql02
Why ?
The first instance was call only "mycluster01" ...
Perhaps because all new instance of virtual server that i install are a "sql
named instance" ?
Thanks.
"Linchi Shea" <linchi_shea@.NOSPAM.ml.om> wrote in message
news:ex9%23QsezFHA.3924@.TK2MSFTNGP14.phx.gbl...
> No matter whether it's clustered or not, each SQL2000 instance has its own
> location for its binaries (well some binaries for the tools are shared).
> You can specify the same path, and the install will create a different
> folder under that path for each instance. For instance, if you specify
> D:\MyDir for the binaries (program files), the install will place the
> binaries under D:\MyDir\MSSQL for the default instance, and under
> D:\MyDir\MSSQL$<InstanceName> for a named instance.
> Check out the section titled "File Paths for SQL Server 2000" in BOL.
> Also, technically you don't really install another virtual server on the
> passive node. Rather, you install another virtual server in the cluster,
> and when you install it, the binaries are placed on all the nodes. You can
> configure the virtual server to run on a particular node in its normal
> operating mode.
> Linchi
> <io.com> wrote in message news:%23c$txrdzFHA.460@.TK2MSFTNGP15.phx.gbl...
>
|||Precisely. Multiple instances on a cluster look and act just like multiple
instances on a stand-alone box. I typically use only named instances on a
cluster just to avoid naming confusion.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<io.com> wrote in message news:%233DO2ipzFHA.268@.TK2MSFTNGP09.phx.gbl...
> Sorry , a lat question :
> i have isntalled the new virtual server and it work fine but i see that
> the new instance of sql virtual server is myclustersql02\myclustersql02
> Why ?
> The first instance was call only "mycluster01" ...
> Perhaps because all new instance of virtual server that i install are a
> "sql named instance" ?
> Thanks.
> "Linchi Shea" <linchi_shea@.NOSPAM.ml.om> wrote in message
> news:ex9%23QsezFHA.3924@.TK2MSFTNGP14.phx.gbl...
>
|||<io.com>@.nirgendwo wrote:

> Thanks you!
[vbcol=seagreen]
> "Linchi Shea" <linchi_shea@.NOSPAM.ml.om> wrote in message
> news:ex9%23QsezFHA.3924@.TK2MSFTNGP14.phx.gbl...
You can review too this MS paper:
http://support.microsoft.com/default...b;en-us;243218
Congrats!
coke.cl [-en-] gmail.com
http://www.foto-digital.cl/
|||:-)
Thanks for you time.
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:uwzLStpzFHA.2132@.TK2MSFTNGP15.phx.gbl...
> Precisely. Multiple instances on a cluster look and act just like
> multiple instances on a stand-alone box. I typically use only named
> instances on a cluster just to avoid naming confusion.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> <io.com> wrote in message news:%233DO2ipzFHA.268@.TK2MSFTNGP09.phx.gbl...
>
|||The only difference between multiple instances on a Clustered installation
versus a standalone is the Virtual Server name.
On a stand-alone, you can have 1 default instance and multiple named
instances, supported up to 15 or 16 named instances, which is true for a
clustered installation too. The reason being that any one node would need
to distinguish between the different binary sets just like a stand-alone,
registry keys, etc.
However, each virtual instance would also need a dedicated cluster group,
which requires a disk resource, IP and NAME.
So, for a stand-alone, you have server (default instance),
server\instance01, server\instance02, . . ., server\instance15. For a
clustered installation, virtual01 (default instance), virtual02\instance01,
virtual03\instance02, . . ., virtual16\instance15.
Sincerely,
Anthony Thomas

<io.com> wrote in message news:e3QVcj2zFHA.464@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> :-)
> Thanks for you time.
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
> news:uwzLStpzFHA.2132@.TK2MSFTNGP15.phx.gbl...
you[vbcol=seagreen]
the[vbcol=seagreen]
cluster,[vbcol=seagreen]
news:%23c$txrdzFHA.460@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
install
>