Hi Team, I need a suggestion in deploying the packages in production server. The production setup has one application(SPS) server and one db server(both are different boxes). One of the packages has to be executed from .net screen and this package has to access the file in the SPS 2010 server. It is possible to call the package which is in DB server? do we need to move the packages on SPS system? were should the packages reside? Regards, Eshwar.

Hi, I do not think that you need to move your package to SPS server only because its accessing a file from that server. You can always confgure the file path. If your server is accessing the databases those are residing on you DB server (Which is one of the server you have), I feel its better to have your package deployed on DB server. Please mark the post as answered if it answers your question

Thanks for clarification.. Sorry for late response... Is there any harm in putting package files in the SPS server? Our architect there will be firewall issues in calling packages which are in db server. Regards, Eshwar.

It doesn't really matter where you store them, but where you call them. The package is loaded and executed on the machine that runs the DTEXEC command. How does the .NET app exactly execute the SSIS package?MCTS, MCITP - Please mark posts as answered where appropriate.

SPS server also has the database and integration services. Regards, Eshwar.

Hi Eshwar, I agree with Koen, it doesn't really matter where you store them, and please refer to the following link about executing SSIS packages : http://www.mssqltips.com/sqlservertip/1775/different-ways-to-execute-a-sql-server-ssis-package/ Thanks, Eileen

Hi Eshwar, If your SPS and DB server both are geographically located in one place, i dont think it would make much of a difference to you. According to MSDB would be beneficial in many ways. Thanks, Khilit http://www.bigator.com