December 6, 2013 at 11:02 am
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.
December 6, 2013 at 11:27 am
what errors are you receiving when you try to start the agent?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 6, 2013 at 12:42 pm
My first thought was, no way would I do this. If the Agent is running on both then it you have no way of know which one will run a job, I think there is also a question about concurrency, what happens if BOTH start a job. I can't think of anything good to come from this..
I think we need to know what errors you are getting.
Worst case is uninstall that SQL instance (yielding a single node cluster), and then re-install it. You lose the second node for THAT instance for a bit but then you get it back..
CEWII
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply