One parent package with a For Each loop that gathers all the appropriate configuration parameter values and passes them to a single child package that takes the configuration parameter values...

Ouch!!

My first thought is that it is a file system access issue for the SQL Agent. But you say you tried a proxy. Was the proxy set up...

I think this is more or less the way I would do it as well. The one caveat that I see is customer level security will have to be...

Check these out

http://www.amazon.com/The-Data-Warehouse-Toolkit-ebook/dp/B006BBLM0Y/ref=sr_1_2?ie=UTF8&qid=1370454024&sr=8-2&keywords=kimball+dimensional+model

http://www.amazon.com/Star-Schema-Complete-Reference-ebook/dp/B003Y8YWAE/ref=sr_1_1?ie=UTF8&qid=1370454024&sr=8-1&keywords=kimball+dimensional+model

http://www.amazon.com/Agile-Data-Warehouse-Design-Collaborative/dp/0956817203/ref=sr_1_4?ie=UTF8&qid=1370454024&sr=8-4&keywords=kimball+dimensional+model

The best way to do this is with package configurations for your connections. Each server can have its own configuration table/file indicating the appropriate connection string for each connection....

Yes, there are 2 values associated with a parameter, the Label and the Value. The Label is what is displayed to the user, the Value is what is passed...

infringement

fatigue

Here comes the sun!

Anyone can cook

missing

The driver we use is

IBM DB2 for i IBMDASQL OLE DB Provider.

If I am not mistaken there is a download, install, and configuration process to get this driver working. ...

This is a hard question to answer because there are so many variables.

Do you have the latest drivers?

Is the pipe, and all the components in between you and the DB2...

I suggest you read these 2 links

http://consultingblogs.emc.com/jamiethomson/archive/2006/12/20/SSIS_3A00_-Using-stored-procedures-inside-an-OLE-DB-Source-component.aspx

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e8645006-899a-40bb-b144-6d65ee0a6290/

So the real challenge is getting the data out of the stored procedure. You could build a work table and then

INSERT INTO dbo.WorkTable

EXEC...