Thanks for the idea. The connection strings are defined in the SSIS package properties so it shouldn't depend on the which account runs it (though it does use the credentials...
In that case, is there another way I can remedy the performance problems of this stored procedure? We have a 3rd party web application that is timing out...