First off, this isn't a great place to post issues with SQL 2005 as DTS is 2000 and previous.
Try the SQL 2005 / Integration Services forum UNLESS these are actually SQL 2000 DTS jobs???
Regardless, the answer will greatly depend on what those packages are actually doing.
For example, one of my bigger packages just completed, hours after its normal time. I found that one of the prod servers it was accessing timed it out, so, failed job.
In other cases, I've found that network latency can cause serious delays.
Consider the sources the pkgs are accessing, as well as the transforms inside. If you don't know what a package is actually doing, it will be difficult to figure out what is suddenly taking so long.
i'm working in SQL server Management Studio 2005 as a application support member, which holds
around 100 jobs scheduled to be run on daily basis. i could able to see few jobs are taking more time to
execute. for ex, if A is a job executing for 5 mins on daily basis which holds around 10-15 steps in it.
Suddenly the execution time differs from 5 mins to 5 hours which is not expected.
Added to this scenario, not only a single job is getting executed for more time.. jobs keep differs day by day. but, as per my analysis all the jobs which are taking more time to execute holds DTS package in it. SQL jobs are getting hanged in this case.
can anyone please help me to sort this out please