RE: Prevent Job Run again
From: Sanchan Sahai Saxena (sanchans_at_online.microsoft.com)
Date: 05/12/04
- Next message: Tom Moreau: "Re: Can you use osql in DTS?"
- Previous message: Partha Mandayam: "Re: DTS Designer Issue"
- In reply to: hngo01: "Prevent Job Run again"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 12 May 2004 21:50:13 GMT
There are a couple of things that you can do:
a) The best thing is to introduce some kind of checks in your process. You
mentioned that if the job runs more than once, you get duplicate data. What
you can do is - although it might be lengtheir - create an excel file with
all the data first and store it in a centralized location. Whenever, that
excel file is found to be already existing, make the job fail. This way,
you will not be able to put another set of duplicate data into your table,
even if you run the job manually.
b) If you want, you can write a Stored Procedure which also has a business
logic built into it. The Sp will not only run the job, but will also keep a
log file of the last time the job was run, along with the status -
failure/success. The next time when the Sp runs, it will first check the
log file and based on the status, can either run the job or cancel it.
Just some of the ways to counter your problem.
sanchans@online.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: Tom Moreau: "Re: Can you use osql in DTS?"
- Previous message: Partha Mandayam: "Re: DTS Designer Issue"
- In reply to: hngo01: "Prevent Job Run again"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
