Automatic failover with SQL Server Standard?

Automatic failover with SQL Server Standard?

Post by anonymou » Tue, 20 Jul 2004 22:47:36


We are trying to implement SQL server failover by using
Windows 2003 "Enterprise" clustering and SQL
Server "Standard" to try to save the cost of SQL Server
Etnerprise. From what I understand we cannot have
automatic failover of the SQL server service with this

Could someone please explaing to me techinically why we
cannot do this:

- Implement W2003 Enterprise OS clustering.
- Install SQL server "standard" installed on both machines
in the OS cluster.
- Have the SQL server service start on the primary node in
the OS cluster and manage the database. Then ...

as part of the OS cluster confifuration, if the primary
node goes down, request that the SQL server service starts
up on the backup node as part of the OS failover.

Can't the clients continue to talk to the SQL server
database since it is not started up on the backup node and
has the same IP address?


Automatic failover with SQL Server Standard?

Post by uttamk » Tue, 20 Jul 2004 23:58:53

As you rightly said, SQL Server 2000 Failover Clustering is NOT supported with SQL Server 2000 Standard Edition. It is fully supported on SQL Server 2000 Enterprise Edition.

You can install and configure any non-cluster aware application as a generic service on a cluster. You can even make notepad clustered as a generic service in a cluster if you like.

I have not seen anybody doing following this approach (using sql server 2000 std edition as a generic service). I wouldn't recommend it. This will be like a custom solution and if you have any issues with the failover
working properly, the support that you will get will be very limited. If you have to work with SQL Server 2000 Standard Edition then I would recommend exploring SQL Server Replication.

To get an idea of what SQL Server 2000 EE Failover Clustering does please refer to the following whitepaper.

Microsoft Whitepaper - SQL Server 2000 Failover Clustering

Cluster Support Policy
Microsoft's Cluster support policy is below

Cluster (General): ;en-us;309395
Cluster (SQL): ;en-us;327518

Best Regards,

Uttam Parui
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:


Automatic failover with SQL Server Standard?

Post by Jasper Smi » Mon, 26 Jul 2004 10:04:56

Note that Veritas support clustering SQL2000 Standard. When I've used it,
it's been just using VCS and not involving MCS at all but I believe it can
sit on top if it as well. I think they've rebranded recently so its called
Storage Foundation High Availability rather than Veritas Cluster Server to
reflect its reliance on Veritas Volume Manager (which is now called Storage
Foundation). I actually prefer the Veritas cluster management tools to the
MS tools and it's a lot cheaper than going to Enterprise Edition if the only
reason you need Enterprise is clustering (and not performance/large memory
support etc).


Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -