As of SQL Server 2000 Failover Clustering, you should be able to use SQL Enterprise Manager, SQL Server Services Manager, Query Analyzer and Cluster Administrator to start/stop SQL Server resources as all
these are cluster aware. This was not true for SQL Server 7.0 Failover Clustering and in that case only Cluster Administrator had to be used to start/stop the SQL Server Services.
Additional Information:
======================
INF: Clustered SQL Server Do's, Don'ts, and Basic Warnings
http://support.microsoft.com/?kbid=254321 Here is the relevant section from the above mentioned Microsoft Knowledge Base article
============================================================================================================================
Start and stop SQL Server services
SQL Server 6.5 and SQL Server 7.0 virtual servers
------------------------------------------------------------------------------
To start or stop SQL Server, SQL Server Executive, or SQL Agent services from a SQL Server 6.5 or SQL Server 7.0 virtual server, you must use the Microsoft Cluster Administrator or the Cluster.exe command line
tool.If you attempt to start or stop services in any other way (for instance, from Control Panel, SQL Service Manager, or SQL Enterprise Manager), the registry may be corrupted, and you may need to uncluster or
completely reinstall SQL Server.The most common sign of having started a service incorrectly is that the service accounts appear as a jumble of ASCII characters.If you need to start SQL Server from a command
line, you must use the Cluster Administrator or Cluster.exe tool to first take the SQL Server, SQL Executive, or SQL Agent services offline.When you start SQL Server from a command line, connectivity takes place
using the virtual server name. The only way to make a local connection is if the resources are owned by the node from which you originally installed SQL Server.
SQL Server 2000 virtual servers
----------------------------------------------------
SQL Server 2000 virtual servers do not have the above restrictions. We recommend that you use SQL Server Enterprise Manager, SQL Server Services applet, or Cluster Administrator to start and to stop SQL
Server 2000 virtual server services. Although you can use Service Control Manager or Control Panel/Service to start and to stop the services without damaging the registry, these options will not cause the
services to stay in a stopped state. Instead, the services will be detected by the clustered server and you will receive multiple event ID 17052 error messages in you SQL Server that are similar to the following:
[sqsrvres] CheckServiceAlive: Service is dead
[sqsrvres] OnlineThread: service stopped while waiting for QP
[sqsrvres] OnlineThread: Error 1 bringing resource online
After you receive these error messages, SQL Server will be restarted by the cluster service. This behavior is expected for these types of errors.
============================================================================================================================
HTH,
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
http://www.microsoft.com/security. 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:
http://www.microsoft.com/protect http://www.microsoft.com/security/guidance/default.mspx
