Hi Alexander,

Thanks for the exta info

Are you running on a 32-bit server? SSIS really needs a 64-bit server
to shine, and even on 64-bit you should remember that BIDS
(devenv.exe) is a 32-bit application, so during development you still
need to run the package using the 64-bit dtexec.exe.

I think your best option in this case is to split up the work that the
package is doing into logical steps, and put each step into a separate
package. The reason SSIS is making the temp files is because it's
running out of RAM and is paging to disk - when this happens the
package is going to be slow, regardless of whether it errors out or
not. If you notice that SSIS isn't making use of all the available
RAM, you might have a couple options (adding more RAM / tweaking
settings and package structure / etc) but the biggest gain will
probably be from splitting up the package.

There are a few very good SSIS performance white papers on the MSDN
site - definitely worth a read if you're dealing with any significant
volume of data.

Good luck!
J