Understanding the Differences between Local and Remote Execution

Package developers and administrators should be aware that there are restrictions related to where an Integration Services package runs.

• A package runs on the same computer as the program that launches it. Even when a program loads a package that is stored remotely on another server, the package runs on the local computer.

• You can only run a package outside the development environment on a computer that has Integration Services installed. You cannot run packages outside of SQL Server Data Tools (SSDT) on a client computer that does not have Integration Services installed, and the terms of your SQL Server licensing may not permit you to install Integration Services on additional computers. SQL Server Integration Services is a server component and is not redistributable to client computers. To run packages from a client computer, you need to launch them in a manner that ensures that the packages run on the server.

For more information about loading and running a saved package, see:

• Loading and Running a Local Package Programmatically

• Loading and Running a Remote Package Programmatically

For more information about running a package and loading its output into a custom program, see:

• Loading the Output of a Local Package

Stay Up to Date with Integration Services For the latest downloads, articles, samples, and videos from Microsoft, as well as selected solutions from the community, visit the Integration Services page on MSDN: Visit the Integration Services page on MSDN For automatic notification of these updates, subscribe to the RSS feeds available on the page.

See Also

Tasks

Loading and Running a Local Package Programmatically

Loading and Running a Remote Package Programmatically

Loading the Output of a Local Package