I'm looking for suggestions on how to handle a situation that occurs
randomly.
I have a Job that runs a dts package every 2 hours that takes 3 minutes to
complete. Once in a while it gets stuck saying that it is running in the
status column of the Jobs node. Once observed a simple matter of stopping
and then starting the job gets it back on track.

does anyone one have some suggestions on how I could programatically stop
the job once it has been running over 4 hours?


I have not been able to determine why it gets stuck running because it is so
infrequent but seems to happen when the results are mort needed by the users.
thanks in advance,

"Jim Abel" wrote:

Take a look at sysjobactivity in msdb. That will give you the start time
with a null completion time for running jobs. If you poll that you should see
if the job has gone over your limit then you can kill it using sp_stop_job.

"Jim Abel" wrote:

Take a look at sysjobactivity in msdb. That will give you the start time
with a null completion time for running jobs. If you poll that you should see
if the job has gone over your limit then you can kill it using sp_stop_job.

"Jim Abel" wrote:

Take a look at sysjobactivity in msdb. That will give you the start time
with a null completion time for running jobs. If you poll that you should see
if the job has gone over your limit then you can kill it using sp_stop_job.

"Jim Abel" wrote:

Take a look at sysjobactivity in msdb. That will give you the start time
with a null completion time for running jobs. If you poll that you should see
if the job has gone over your limit then you can kill it using sp_stop_job.

"Jim Abel" wrote:

Take a look at sysjobactivity in msdb. That will give you the start time
with a null completion time for running jobs. If you poll that you should see
if the job has gone over your limit then you can kill it using sp_stop_job.

"Jim Abel" wrote:

Take a look at sysjobactivity in msdb. That will give you the start time
with a null completion time for running jobs. If you poll that you should see
if the job has gone over your limit then you can kill it using sp_stop_job.

"Jim Abel" wrote:

Take a look at sysjobactivity in msdb. That will give you the start time
with a null completion time for running jobs. If you poll that you should see
if the job has gone over your limit then you can kill it using sp_stop_job.

"Jim Abel" wrote:

Take a look at sysjobactivity in msdb. That will give you the start time
with a null completion time for running jobs. If you poll that you should see
if the job has gone over your limit then you can kill it using sp_stop_job.