Post reply

using a relative path to a configuration file in SSIS

  • September 16, 2008 at 8:57 am

    #192836

    I would like to be able to have configuration files that stay with the package but use a relative path such as \bin, same as how the build path is specified.

    Is this possible and how?

  • September 16, 2008 at 3:09 pm

    #872725

    Found this posting to accomplish the same thing if anyone is interested

    http://jessicammoss.blogspot.com/2008/05/ssis-configuration-to-configuration-to.html

  • November 6, 2014 at 3:48 am

    #1756928

    I did below workaround for relative path issue:

    BIDS 2008 doesn't work on relative path,may be some kind of bug

    If you try to enter the relative path , on clicking next it calculates the whole path.

    The best workaround is to open the SSIS xml search for the path you just entered and make it as relative.

    For eg.

    In BIDS package configuration window you have entered path as:

    c:\BIDS\abc.config

    Go to Package xml search for above line and replace with :

    ..\BIDS\abc.config

    and save it.

    the work is done, now if you reopen the SSIS in the BIDS window and check the package configuration window it will show the relative path.

    To see the xml , go to the solution explorer window of BIDS, Right click the package and click on view code.

    Hope this will help

  • November 6, 2014 at 7:17 am

    #1756993

    Wow... a blast from the past. Yeah got it working thanks :cool:. We used a system enviro var setup on each server and each dev workstation.

    This pointed to the location for the configs. That way we could have configs specific to where the package was run or developed.

    But... Now with 2012 that whole config setup is out the window anyway. Using project deployment model and the server Environments. But we did lose the functionality on the development side. Now the best thing seems to be for the developers to use server aliases (that are all the same) and build the project using those names so when we run locally (debug) it defaults to the param value since there is no server environment and they dont need to be messing with param values. Oh yeah we all run our own dev SQL instance. 😀

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply