Tom Frohman
February 9th, 2005, 09:35 AM
I have a job called updateps which is started by the insert and update triggers on a table.
If another record is inserted or deleted before updateps is finished, I get an error message saying the job couldn't be started. Is there a way I can check within the trigger procedure if updateps is already running? Then I could not start the updateps job. If updateps is already running, it will process the most recently inserted/updated records and I don't need to start updateps again.
I put the processing into a job so that it wouldn't hold the user up while the record is processed. Otherwise, I could just do the processing in the trigger.
What stored procedure or command would I use to get the running status of the job?
Thanks, Tom
If another record is inserted or deleted before updateps is finished, I get an error message saying the job couldn't be started. Is there a way I can check within the trigger procedure if updateps is already running? Then I could not start the updateps job. If updateps is already running, it will process the most recently inserted/updated records and I don't need to start updateps again.
I put the processing into a job so that it wouldn't hold the user up while the record is processed. Otherwise, I could just do the processing in the trigger.
What stored procedure or command would I use to get the running status of the job?
Thanks, Tom