Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
aspeckman
Starting Member
10 Posts |
 Posted - 2013-12-06 : 13:04:48
|
| We are having trouble with SQL Agent in a cluster, on one node it doesn't start. I have not been involved in the root-cause analysis, but I was thinking of unclustering Agent. Never done it before.What is the impact of running agent on each node with automatic, so its running on both servers. So, when SQL Server is running on Node 1, executing jobs, then fails over to Node 2, can't it just use the Agent service running on that server instead?Thanks. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2013-12-06 : 13:18:10
|
| I don't see how that would work. The SQL instance is pointing to a shared disk, that disk is only available on one node at a time. The SQL Agent's files are on that disk. So you won't be able to start the Agent on the passive node.I would recommend opening a support case with Microsoft on this. It's probably an easy fix. You could try posting the error that's in the Event Log.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
|
|
|
Uncluster Agent, set to automatic on each node