Orchestrator fail over caused by long query on database
We have Orchestrator setup as fail over cluster.
We have quite a few runbooks start with Monitor activity.
And recently we found when we do a long select query the server has failed over, and we see multiple job instances with started.... lines.
The select query we did is a to search centain error string in the programoutput table columns.
The query runs over 12 minutes. that caused the server has failover.
Why is that, any place or settings that we can change the server not fail over when we doing long select queries?
I have never seen such a setting, maybe it’s the time to contact Microsoft CSS support.
Sign in to comment