We have an SQL2005 cluster that is running ESRI ArcSDE. ESRI suggests that it depends on SQL Agent and this is how we have the resource dependency setup. We had a situation that we had to take SQL Agent offline and then abck online and this caused ArcSDE
to stop as well. ArcSDE needs SQL to be active rather than SQL Agent and there could be other occasions that SQL Agent is in trouble and needs to be stopped/started as is used for our database backups. Is there a better dependency we could use or have we setup
the dependency in the clustered services incorrectly?
View Complete Post