We took databases offline last night. Ran this to disable jobs:
USE MSDB;
GO
UPDATE MSDB.dbo.sysjobs
SET Enabled = 0
WHERE Enabled = 1;
GO
We then brought the databases back online and re-enabled the jobs:
USE MSDB;
GO
UPDATE MSDB.dbo.sysjobs
SET Enabled = 1
WHERE Enabled = 0;
GO
But the jobs did did not kick off. If I go and manually disable / enable the jobs they start to work.
Looking at the jobs they all say enabled. Both from inside the job properties as well as in MSDB.dbo.sysjobs. The interesting thing is that in the job properties as well as MSDB.dbo.sysjobs the date_modified only shows the date/time which we disabled the job. That must be a clue? Also, SSMS was having some odd connectivity issues. But how can it say enabled yet not run?