Is there a way I can tell which account turned off the SQL Server Agent?

Question

I have a little situation that I'm left searching for answers for. Some person or process (I'm being generous as I don't, for one second, believe the culprit is a process) stopped my database server's SQL Server Agent several days back and I'd like to run down who or what did that...and I have no idea where to even start to look.

To be clear: it wasn't a job that was stopped, it was the SQL Server Agent that runs all the jobs that was stopped. I'd very much like to sort out which login was responsible for stopping it. We're running SQL Server 2014 SP3

Any ideas, pointers, explicit directions, séance results, tea leaf readings would be most appreciated.

Answer 1

Hi，Heath, Craig

Welcome to Microsoft Q&A fourm!

I'm glad you found the cause!

Checking the Windows Event Log is the preferred method for troubleshooting unexpected stops of Windows services.

Additionally, for SQL Agent service specifically, you can also review the SQL Agent logs to troubleshoot anomalies.

Moreover, a reliable approach is to configure automatic restart.Refer to this link.

Lastly, we welcome you to generously share your experiences, as this will help other friends who have similar issues. We also welcome you to start new threads on the forum.

Best Regards,

Mikey Qiao

---

If you're satisfied with the answer, don't forget to "Accept it," as this will help others who have similar questions to yours.

Answer 2

N/M. I sifted the server logs and found the issue.