• The reason I was asking is i had a similar problem when I would failover our mirror databases. The code that was enabling/disabling the database specific jobs wasn't "working". Where the jobs were being disabled, they kept working and where the were being enabled they would run.

    I had to modify my code to use the sp_update_job stored procedure in the msdb database. Turns out that SQL Server Agent caches the information and this stored procedure forces a notification to SQL Server Agent.