Hi all,
I've have a simple question. After running the SSIS deployment utility to install a couple of SSIS packages into a SQL Server, is there a way of determining programmatically (at some later stage) where the dependency files (in my case a simple xml configuration file) for the SSIS packages were installed (if the user chose not to install it into the default location).
Thanks,
Johan
Johanw581996 wrote:
Hi all,
I've have a simple question. After running the SSIS deployment utility to install a couple of SSIS packages into a SQL Server, is there a way of determining programmatically (at some later stage) where the dependency files (in my case a simple xml configuration file) for the SSIS packages were installed (if the user chose not to install it into the default location).
Thanks,
Johan
Absolute paths are required when pointing to things external to the package (XML configuration files, etc...), so the path should never change from when the package was developed.
No comments:
Post a Comment