February 1, 2010 at 2:01 pm
We have a DTS Package that has been running for several years. Lately it seems to be having an issue where it looks as if it's completed successfully but it actually has not. There are several steps to the job but one step is to create a 'Job Is Running' text file in a directory. It then reads the same directory for files to process, if they exist, it moves the files to an InProcess directory. After this it calls a DTS Package to interrogate the files. Once this is done a DTS Package is called next to FTP the files to the backend system. Once this is done the files are moved to the Archive directory and the 'Job is Running' file is deleted.
For several months now we have seen where the 'Job is Running' text file is not being deleted and the files are still in InProcess directory. If you look at the Job History the job seems to think it finished processing everything and ends successfully.
We think there might be an issue with the Scheduler. We moved a new package into the system and scheduled it. The scheduler executed the job at odd times, not according to the schedule. I turned that new job off and it never ran again.
This morning I moved the original package and job over to a new server with a new SQL Server installation. I Disabled the original and new package on the original server. I did not schedule anything. I wanted to watch the system and execute it manually. So at this point, nothing is scheduled and the 2 jobs on the original server have been disabled (Right click on the Job and choose 'Disable Job'.)
This afternoon I see the original job on the original server is executing and sure enough the files are stuck again. I went to the original server and checked on Job History and nothing states that it is running. I checked the new job on the new server and that did not execute either.
Now I am thinking that my issue might really be with the scheduler.
1) Has anyone else experienced this?
2) Has anyone else discovered a resolution for this?
3) How do I ensure that the job will not kick off once I disable it? I went in and disabled it in the schedule as well but I am not sure now that that will take care of this issue.
Any help will be greatly appreciated!
Thank you,
Nadine Comiter
747-369-7026
February 2, 2010 at 3:48 am
Once you disable a SQL job, it is disabled.
You have an issue with something else firing off that package. Something like a stored procedure can fire off a DTS package. I would also check all the jobs, make sure that is not a different SQL job firing off the package. Nothing happens by itself.
Andrew SQLDBA
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply