I have a SQL 2K job that retries a DTS package several times. This DTS
package, about midway through, has an Execute SQL task that calls a
stored procedure that does a mass update. When this task runs, the
mass update hangs. If I look at the update "Process" under "current
activity," it shows the CPU and I/O increasing (CPU got up to
4,000,000), but the memory was at 0. I eventually had to stop the job.


Why is this process showing 0 memory as the CPU and I/O steadily
increase?

Is there maybe a flaw in how I set up my connections in the DTS
package?

My DTS package has 5 SQL connections and 5 DB2 connections. Two of the
5 SQL connections get used more than once. The other 3 only once a
piece.

Thanks in advance for any input,

Brad