| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
Understanding the Differences between Local and Remote Execution |
Understanding the Differences between Local and Remote Execution |
chugugrace |
chugu |
03/17/2017 |
sql |
integration-services |
reference |
|
[!INCLUDEsqlserver-ssis]
Package developers and administrators should be aware that there are restrictions related to where an [!INCLUDEssISnoversion] 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 [!INCLUDEssBIDevStudioFull] on a client computer that does not have [!INCLUDEssISnoversion] installed, and the terms of your [!INCLUDEssNoVersion] licensing may not permit you to install [!INCLUDEssISnoversion] on additional computers. [!INCLUDEssNoVersion] [!INCLUDEssISnoversion] 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:
For more information about running a package and loading its output into a custom program, see:
Loading and Running a Local Package Programmatically
Loading and Running a Remote Package Programmatically
Loading the Output of a Local Package