Re: Type of Cluster?



A multi-instance cluster would be the correct solution. You can run each
instance on its own host node during normal operating conditions. During a
failover event, you would host multiple SQL instances on a single node. I
would purchase a fourth node and have a 3-instance, 4-node cluster. That
way, any single node failure will cause the failed instance to move to the
empty node. This requires a bit of configuration work, but is well within
the capabilities of SQL Server. I have built and operated just such a
cluster in the past with a high degree of success.

A SAN is a required element for a cluster with more than two nodes.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"rui" <rui@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3F786FD2-AFE4-4F6C-A1A4-71C005C68977@xxxxxxxxxxxxxxxx
> Hi,
>
> I have 3 databases on 3 seperate SQL 2000 servers, all are used heavily.
> There is no high availablity solution.
>
> I was thinking of placing the databases in Windows 2003 Cluster. If I do
> that, in terms of performance shouldn't I use an active\active
> configuration
> (i think it's called multi-instance nowadays). What I am trying to say is
> that each server in the cluster will maintain its own database.
>
> Wouldn't I need a beefed up server to put all databases on a single node
> in
> an active\passive cluster.
>
> I also have use of a SAN
>
> Thanks
>
>


.



Relevant Pages

  • Re: Cluster will not fail over.
    ... As far as the TCP/IP issue goes, you had to rebuild the cluster and were not ... able to restore the master database. ... the entire installation configuration just as if nothing was running on it. ... > This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster will not fail over.
    ... This worked bringing up the sql server in minimal mode. ... > Start SQL Server in single user mode with trace flag -T3608. ... > SQL from recovering anything except the master database. ... > You didn't mention whether you blew the cluster away or not or just ...
    (microsoft.public.sqlserver.clustering)
  • Re: Migrate existing standalone to cluster
    ... To create a database with a case-sensitive collation, ... Finally, remove the standalone. ... Columnist, SQL Server Professional ... >> the DB's to the cluster? ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster will not fail over.
    ... I honestly did not have time to investigate as to why the cluster would not ... SQL Server would immediately turn off. ... >> SQL from recovering anything except the master database. ... use files copied from another installation at the exact ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)