that is correct
A instance (= virtual server = a cluster group) is only online on 1 node in
a server cluster
You can however run a second instance (= a second virtual server = a second
cluster group) on another node, however this instance has its own disk
resources and its own database(s).
this is the "shared nothing" model from MSCS
the real limitation is that you cannot have two Windows Servers accessing
the same NTFS volume. This is a NTFS limitation. If you have more than one
Windows Server accessing the same NTFS volume, it will lead to NTFS
corruption and more than likely data-loss. The cluster service manages the
disk resources, so only one node in the cluster will have ownership, and
therefore access, to the NTFS volume.
I hope this explains it
Rgds,
Edwin.
[quoted text, click to view] "JayKon" <JayKon@discussions.microsoft.com> wrote in message
news:07292967-4896-4169-8ECF-F38933589435@microsoft.com...
> I was reading the Microsoft white paper
>
(
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.msp x) on clustering and noticed something I didn't expect.
[quoted text, click to view] >
> It seems to say that only one node of a cluster may be used at a time and
> that it is not for (any kind of) load balancing. The only apparent
advantage
> over log-shipping being an automatic failover.
>
> Is this correct? If so, it seems rather strange to me (yes I understand
the
> problem of inserts with a primary key across servers).