Why does the Execute Package Task in SSIS always fail when set to execute in-process?
Having ExecuteOutOfProcess = False always results in that the package fails when run from within BI Studio.
I have also tried it from Command Line using dtexec., same results.
The problem with setting ExecuteOutOfProcess = True all the the time and running from within Bi Studio is that an enourmous amount of processes is created, none of which die because SSIS runs in Debug mode, another problem which is there doesn't seem to be a way to run it in Release mode so as not to get so many Dtexec processes, which ultimately results in having the Server die.
By Dying I mean, thrashing of the CPU & Memory. Page file to extreme limits.
And yes, the hardware should be able to take much more than what SSIS is supposed to eat. Dual 3GHz Xeon & 4GB of Ram.
Thank you.
My kind regards,
Eng. Ahmad Alkilani
Eng. A. Kilani wrote:
Having ExecuteOutOfProcess = False always results in that the package fails when run from within BI Studio.
What error message do you get?
there doesn't seem to be a way to run it in Release mode so as not to get so many Dtexec processes, which ultimately results in having the Server die.
If you start the package using Ctrl-F5, BIDS starts one dtexec.exe process. When the package ends, just close this console window. I don't see how you can get numerous dtexec.exe processes. Do you mean dtshost.exe processes (these may be left behind for some time if parent dtexec.exe process is forcefully killed)?
|||Problems may already be solved, but for people like me who are looking for a solution to this problem: If ExecuteOutOfProcess is set to True bugs in the childpackage doesn't cause the parent package to stop because of this bug. It will also be possible for a single package to use more then 2GB of memory on it's own.
No comments:
Post a Comment