In our recent articles published on this forum, we have been discussing different methods of executing SQL Server 2012 Integration Services packages deployed by employing the traditional Package Deployment Model, focusing in particular on those stored in the .dtsx file system format. While in a majority of cases the process we have described works as expected, there are some caveats that need to be considered if your tend to store SSIS packages on network-accessible file shares (rather than locally on the same system where packages are running). We will discuss the technical reasons for these considerations and present a couple of methods for addressing them.
↧