File Connection Manager Path Headache

  • Hi All,

    In my SSIS package I have a number of pre-requisite functions and stored procedures to add, which are stored as SQL files in the package, and each is executed using a File Connection Manager in an Execute SQL task.

    The paths appear to be hard-coded in the package. When moving from development to test servers I have to manually reset the paths.

    Does anyone know a way of chainging the file paths easily, or making them relative to the package location?

  • They are relative to the server that runs the package, so if you put them on your local C drive, the server versions could be on the local C drive of the server.

    However, you are describing the purpose of package configurations. I would suggest you look into them in books online. They can be a little tricky, but once you have used them a couple of times they are pretty reasonable to deal with.

  • I have a video on oledb connection mgr and config files... the concept is the same for files.

    check it out if you like...

    http://midnightdba.itbookworm.com/SSISConfigFileConnString/SSISConfigFileConnString.html

    Watch my free SQL Server Tutorials at:
    http://MidnightDBA.com
    Blog Author of:
    DBA Rant – http://www.MidnightDBA.com/DBARant

    Minion Maintenance is FREE:

  • Thanks. Good video I found it useful. Keep burning the midnight oil 🙂

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

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