Re: SQL Server Clustering in Windows 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Todd Harrington (anonymous_at_discussions.microsoft.com)
Date: 06/07/04 

Date: Mon, 7 Jun 2004 06:54:22 -0700

Hi Rod,

Thanks for the reply. That is a big help. I have one more
follow up question.

Can we purchase Windows 2003 "Enterprise" and SQL Server
2000 "Standard" and still utilitize the Windows 2003
clustienr features? Could we set up a 2003 cluster with
this configuration where one node is active and runs the
SQL Server "Standard" service. The other node is the
standby node in the cluster and if the primary node fails,
the standy node will take over the IP address and startup
the SQL server service. Client requests will now be
handled by the Standby node which will have the IP address
that the client expects and can manage the SQL Server
datasbase. I may be down for few seconds when the failover
happens.

I understand I need Windows 2003 "Enterprise" but do I
NEED SQL server "Enterprise" too? Can I use SQL
Server "Standard"? What do I gain/lose?

Thanks,
Todd

>-----Original Message-----
>answers inline below:
>
>"Todd Harrington" <todd.harrington@suntroncorp.com> wrote
in message
>news:17d3d01c4499c$23bf4540$a401280a@phx.gbl...
>>
>> Hi,
>>
>> We are running SQL Server 2000 on a Windows 2003 Server.
>> The Windows 2003 Server is connected to a RAID disk
array.
>> The Windows 2003 server is a single point of failure. We
>> want to add a second Windows 2003 box and connect it to
>> the RAID as a backup node.
>>
>> It seems there are two ways to do this:
>>
>> 1) Implement Windows 2003 Clustering (need to move to
>> Windows 2003 Enterprise??) where both nodes share an IP
>> address. If the Primary node in the cluster fails the
>> backup node in the cluster can start the SQL server
>> service and handle requests. Is this one way to do this?
>> Is this a good way?
>>
>
>You will need Enterprise of Windows and SQL for
Clustering. This will allow
>you to share an IP and Network Name for SQL. This is an
excellent way to go.
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;243218 is a great
>place to start learning more. Its for Windows 2000, but
its still the same.
>
>> 2) It looks like SQL server Enterprise
>> implements "Failover" as a feature. This is not included
>> in the "standard" edition. The Enterprise edition is
much
>> more expensive and I am not sure what it gains us over
my
>> first solution.
>>
>
>This is actually the same as number 1.
>
>Cheers,
>
>Rod
>
>> Any help explaining the differences between the two
would
>> be appreciated.
>>
>> Thanks,
>> Todd
>
>
>.
>

Relevant Pages

  • Re: Slow booting xp home.
    ... Changing the boot order to boot first from your hard disk might save you a half second, but you won't be able to boot from a CD until you change it back - and the time spent to do that will erase any previous time saved. ... 2- Consider what software you really want to start with Windows and also how you've configured your applications at startup ... Installing and Registering Visual Studio Express Editions Smart Device ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: How to cluster sql in a 2003 cluster
    ... For the most part setup on a Windows 2003 cluster is identical to setup on ... SQL Server 2000 does not support mount points. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Upgrading Windows 2000 cluster to Windows 2003 Cluster.
    ... I made absolutely sure I had all the drivers and software for Windows ... worked as a cluster host node, I upgraded its peer node, also in-place. ... You must re-run any service packs and hotfixes after the install when you ... SQL server 2000 which we installed it as a virtual server. ...
    (microsoft.public.sqlserver.clustering)
  • Re: What do I need to cluster SQL under Windows 2003
    ... The second machine is thus in an standby mode in case machine one fails. ... This is less expensive than implementing a cluster. ... the cluster fails the backup node in the cluster can start the SQL server ... The Enterprise edition is ...
    (microsoft.public.sqlserver.clustering)
  • Quorum drive on a network share
    ... I set up a test system for SQL Server 2000 clustering on ... Windows 2000 Enterprise with a two-node cluster running generic workstation ... Can anybody tell me how I might have achieved the original setup on Windows ...
    (microsoft.public.windows.server.clustering)