Jobs that run SSIS packages still executing after being disabled

[Brian Hman]

Hi,

I had two jobs that ran SSIS packages on SQL Server 2005, and I had disabled
both of them. Both jobs had a schedule that had them running every 25
minutes.
Since they were disabled, I assumed they would no longer run, but I realized
that they still were and they were causing some contention with some of our
cubes in SSAS.

Is this expected behavior? The jobs are disabled but since they have
schedules defined they'll still run the SSIS package? This was completely
unexpected behavior for me, and I want to be sure that I don't need a patch
or some sort of configuration change.

Thanks,
Brian

[Peter Yang]

Hello Brian,

Based on my experience, I don't think this is the expected behavior of SQL
Server when scheduled jobs are disabled.

You may want to restart SQL Server to see if the issue persists.

If the problem still occurs, please run SQL profiler to trace the job
execution and make sure it's started from the jobs that you have disabled
their schedules.

In case you need some reference for profiler:

Using SQL Server Profiler
http://msdn2.microsoft.com/en-us/library/ms187929.aspx

SQL Server Profiler Reference
http://msdn2.microsoft.com/en-us/library/ms173757.aspx

Please let's know if you have any update. Thanks.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.