We help IT Professionals succeed at work.

Controlling SQL Server Agent on a Windows 2003 cluster

373 Views
Last Modified: 2010-04-19
We are running a Windows 2003 failover cluster with SQL Server 2000 Enterprise.  Where should SQL server agent service be stopped so as not to initiate a failover? From Services for the Virtual server? From Enterprise Manager?
Comment
Watch Question

Retired
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
To be more specific, our DBA needed to stop the SQL SERVER AGENT service. He stopped it through Enterprise Manager. When he did this all resources in the cluster group failed over to the next node. Our DBA did not know why this happened and said he had stopped the service this way before and the cluster had not failed over, but the the SQL Server Agent service stopped.
The check box is set to Restart but has not changed.
65tdRetired
CERTIFIED EXPERT

Commented:
One would have to review the cluster log from time that event occurred, but suspect that service was in use and when stopped the cluster could not restart the resource so it restarted the group on the secondary node.

Author

Commented:
Does it matter where the SQL Server Agent service is stopped/started/restarted on a cluster?
From where should the SQL Server Agent be controlled on a cluster?
Where should all SQL services be controlled from on a cluster?
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.