I agree Mike. At work we use all active/passive clusters (4 total clusters
with 2 nodes in each) and run only a single instance on each active node. We
are doing a mass db consolidation project now and will likely go the path of
a multinode cluster as that will best suit our business needs.
Do you run different coalition settings on your 4-6 instances per node?
Thanks,
Todd
"Mike Epprecht (SQL MVP)" wrote:
Hi
No, Same collation. For us, multi-instances are there for security (bank),
to keep everyone away from each other.
It also makes it easier to add more nodes if we need to, so we then move the
instances around.
Once you start to have more than 2 busy instances, you better have a decent
SAN (EMC, biiiig EMC's) that can sustain the throughput. Multi fiber cards,
multi paths etc.
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
> I agree Mike. At work we use all active/passive clusters (4 total clusters
> with 2 nodes in each) and run only a single instance on each active node. We
[quoted text clipped - 57 lines]
> > > > >
> > > > > Thanks,
Geoff N. Hiten - 24 Feb 2005 02:52 GMT
I agree 100% with Mike. I run a large N-1 cluster (N Nodes, N-1 Instances)
so I have one stand-by node for three active instances. I have scripts to
change the cluster failover order depending on what maintenance is
happening. I also can change memory settings and collapse the cluster on a
single node during low activity times for host node maintenance. It takes a
few extra steps to manage a large, multi-instance cluster, but the same
principles apply.

Signature
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
> Hi
>
[quoted text clipped - 89 lines]
> > > > > >
> > > > > > Thanks,