Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 354
  • Last Modified:

Controlling SQL Server Agent on a Windows 2003 cluster

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?
0
KirkSamuels
Asked:
KirkSamuels
  • 2
  • 2
1 Solution
 
65tdCommented:
From cluster administrator select properties of the resource, then the Advanced tab, select the Do not restart check box.
0
 
KirkSamuelsAuthor 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.
0
 
65tdCommented:
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.
0
 
KirkSamuelsAuthor 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?
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now