June 10, 2008 at 4:26 am
Hi
We have around 200 DTS packages running as scheduled jobs on our SQL2000 box. Recently jobs have just stopped running. The jobs list shows them as enabled, but they simply are not run.
This is obviously causing lots of problems with data not being loaded into systems and customers are getting rather peeved! The problem is that keeping track of which jobs should be running on any given day is a huge task and things get missed.
Has anyone ever heard of a SQL box doing this before? At the moment we are looking at developing a complete logging solution which will record last run times, success rates and next run times so we can tell for sure whats going on with each job, as we have NO faith in what the jobs list is telling us. This is a big development though, especially as every DTS job would have to be amended to log to this system.
Any help would be greatly appreciated.
June 10, 2008 at 4:31 am
Are they failing? Or just not even trying to run?
June 10, 2008 at 4:39 am
Not even trying to run.
We also have some tasks displayed in the jobs list which permanently say they are currently running. There's no activity from them, and if I right-click > Start Job they run successfully. I've a feeling the whole job scheduling bit of SQL might be messed up but I need to go though all the other available options before I try to get the server tech guys to reinstall anything.
June 10, 2008 at 8:42 am
Hi Chris,
Is sql agent service started?
Regarding logging solution you can make use of logging options available under sql agent job and as well as dts package logs(can be saved at server level means event viewer logs or package level and also at filesystem level means in a notepad file on server drive).
Manu
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply