The package will always run in SQL Server memory space (unless you have installed Integration Services as a separate instance independently – and if you have there will be a licensing issue). The upside is as a developer you can deploy and test new versions by just copying the new version of the package (*.dtsx) to the file repository which can take seconds rather than days waiting for the DBA to get off his bottom. The downside is you will need a file depository area either on the SQL Server box or on an (application) server that SQL Server can access to load and run the packages. By far the best approach is to execute the packages from files using the DTEXEC command. The problem with the first approach is there is too much dependency on the DBA to install the packages into msdb and keep track of version control. SSIS packages can deployed to run within SQL Server (the msdb) database or as stand alone files which can be executed. Any plaudits for this article should be directed to Nigel as these techniques were developed by him. Executing SSIS Packages continued - Simple Talkįollowing on from Nigel Rivett‘s article on three different approaches for running SSIS packages I thought I would share with you some techniques which Nigel showed me while I worked along side him on a recent contract.

Download sample ssis package