This project has moved. For the latest updates, please go here.

Fix Relative Paths

This page has been moved to GitHub and can be found here.

This feature is helpful in setting up packages to use relative paths in connection managers and in the path to dtsConfig files. It was mainly coded to workaround this bug in SQL2008, but it can also be helpful in SQL2005.

For more information about using relative paths in SSIS, see this blog post.

This feature adds a "Fix All Relative Paths" button to the Package Configurations dialog:

FixRelativePathsPackageConfigurationDialog.png

Clicking that button will change full paths (i.e. "c:\Directory\test.dtsConfig") to relative paths (i.e. "test.dtsConfig") if the following are true:
  • If the working directory for the current Visual Studio process is the same directory as the current package.
  • If the package configuration is an XML file and the dtsConfig file is in that same directory.

This feature can also be run on multiple packages simultaneously by using the right-click menu item on the project node in Solution Explorer:
FixRelativePathsMenu.png

When selected, BIDS Helper will scan all open packages. Inside each package, it will scan all XML file package configurations and all connection managers looking for full paths which point to a file in the same directory as the package. The restriction mentioned above about the working directory for Visual Studio still applies.

The results of this command can be seen in the Output Window:
FixRelativePathsOutputWindow.png

Last edited Oct 2 at 4:46 AM by furmangg, version 6