One of our servers is getting the SQL Server Agent job that does transaction log backups disabled with no apparent reason. It has happened sporadically, twice in the last 30 days or so, precisely after 3:00 AM. So, the question is: Has anyone ever experienced specific SQL Server Agent jobs being disabled spontaneously like this? (It's obvious something is disabling the job automatically.) Does anyone have any theories why/how this would happen? Any insights appreciated. Best, Raphael.


There are a lot of things to look at, but what I would to first is, enable an extended event or a SQL Audit that captures the events related to SQL Server Agent jobs.

There is already a good question about that on here:

SQL Server Agent Logging Actions and Changes done to Jobs

And also check for last modified date: select name , enabled , date_modified from msdb.dbo.sysjobs where enabled = 0

  • Thank you much for your reply Fabian. But as per in the original post, I already know when this is happening: "precisely after 3:00 AM." The solution in the link appears overkill, but I might go that route if the other onces do not pan out. Yes, I know there is a lot to look at. But my main question was "Does anyone have any theories why/how this would happen?" As in: "Has there been anyone experienced this issue before so they can provide insights as to what could trigger this kind of issue?" – user1596979 Dec 7 '19 at 18:05
  • @user1596979 - nothing out of the box will do this. There is some job setup, or some piece of software running that is disabling the job. – Max Vernon Dec 9 '19 at 19:59

Not the answer you're looking for? Browse other questions tagged or ask your own question.