We've got DTS running to duplicate our data from our main Oracle server
to our website MSSQL database server. Some of our jobs run as
frequently as a 10 minute interval and 99% of the time it works great.
These little jobs run quick (about 2 seconds long).

Sometimes however, the jobs seem to get stuck. The job will take up to
48 hours to "complete" and I get an email message saying the job
failed. However, when I go to look at the logs, strangely, all the
steps appear to have completed successfully for the job. However,
during the 48 hour interval, the package was not run again on the
scheduled 10 minute interval until it "failed".

We would really like to have DTS as something we can rely on.

FIX: DTS Scheduled Job Does Not Complete After First Run
(http://support.microsoft.com/default...b;en-us;290077)

PRB: A DTS Package Raises Exceptions or Stops Responding When You Run It as
a Scheduled Job
(http://support.microsoft.com/default...b;en-us;318819)


Threading and can cause intermittent problems. Setting stuff to execute on
main thread when required does the trick.

--
Darren Green
http://www.sqldts.com
http://www.sqlis.com

"Aaron" <amilner (AT) racltd (DOT) com> wrote

Your awesome. Thanks!