I swear there is a way in SQL 2000 to have a SQL Server Agent job (that runs
a DTS) to stop running if it's been running for X minutes. I can't find it
though. I thought it was just a checkbox and a field for a number somewhere.
any ideas?

That doesn't ring a bell to me but I am always learning....
Let's call the job you want to monitor - job A
What if you created a new job (B) that would start X minutes after A started
and query the system tables (or sy sviews if you are familiar with them) and
send an sp_stop_job if A is still running?

If you do this, just be sure to make a note in Job A's description noting
the dependency and if you change the schedule of A, change the schedule of B.

--
~lb


"Rich" wrote:

That doesn't ring a bell to me but I am always learning....
Let's call the job you want to monitor - job A
What if you created a new job (B) that would start X minutes after A started
and query the system tables (or sy sviews if you are familiar with them) and
send an sp_stop_job if A is still running?

If you do this, just be sure to make a note in Job A's description noting
the dependency and if you change the schedule of A, change the schedule of B.

--
~lb


"Rich" wrote:

That doesn't ring a bell to me but I am always learning....
Let's call the job you want to monitor - job A
What if you created a new job (B) that would start X minutes after A started
and query the system tables (or sy sviews if you are familiar with them) and
send an sp_stop_job if A is still running?

If you do this, just be sure to make a note in Job A's description noting
the dependency and if you change the schedule of A, change the schedule of B.

--
~lb


"Rich" wrote:

That doesn't ring a bell to me but I am always learning....
Let's call the job you want to monitor - job A
What if you created a new job (B) that would start X minutes after A started
and query the system tables (or sy sviews if you are familiar with them) and
send an sp_stop_job if A is still running?

If you do this, just be sure to make a note in Job A's description noting
the dependency and if you change the schedule of A, change the schedule of B.

--
~lb


"Rich" wrote:

That doesn't ring a bell to me but I am always learning....
Let's call the job you want to monitor - job A
What if you created a new job (B) that would start X minutes after A started
and query the system tables (or sy sviews if you are familiar with them) and
send an sp_stop_job if A is still running?

If you do this, just be sure to make a note in Job A's description noting
the dependency and if you change the schedule of A, change the schedule of B.

--
~lb


"Rich" wrote:

That doesn't ring a bell to me but I am always learning....
Let's call the job you want to monitor - job A
What if you created a new job (B) that would start X minutes after A started
and query the system tables (or sy sviews if you are familiar with them) and
send an sp_stop_job if A is still running?

If you do this, just be sure to make a note in Job A's description noting
the dependency and if you change the schedule of A, change the schedule of B.

--
~lb


"Rich" wrote:

That doesn't ring a bell to me but I am always learning....
Let's call the job you want to monitor - job A
What if you created a new job (B) that would start X minutes after A started
and query the system tables (or sy sviews if you are familiar with them) and
send an sp_stop_job if A is still running?

If you do this, just be sure to make a note in Job A's description noting
the dependency and if you change the schedule of A, change the schedule of B.

--
~lb


"Rich" wrote:

That doesn't ring a bell to me but I am always learning....
Let's call the job you want to monitor - job A
What if you created a new job (B) that would start X minutes after A started
and query the system tables (or sy sviews if you are familiar with them) and
send an sp_stop_job if A is still running?

If you do this, just be sure to make a note in Job A's description noting
the dependency and if you change the schedule of A, change the schedule of B.

--
~lb


"Rich" wrote: