I have an ssis package, that when I run it from the virtual server (the package is deployed on the catalog) and I use a job to run the package it takes 18 hours.
I have set up another server (very small one called TEMP), is also a virtual server and deployed the same package there. When I run the package from the small server it took less than 1 hour.
The package calls data from an oracle server and copies it to the sql server (the server name is TEST).
We can see that we we fire up the package from TEST itself, the network is not fully utilized, therefore the package takes very long.
If I fire up the package on TEMP (I take data from oracle and write it on TEST, I just use TEMP to run the package). the network is fully used.
I am not sure what is preventing the network to receive info when the package is running on itself.