locked
deployed package and its configuration file RRS feed

  • Question

  • I deployed a package to the server. The way I deployed it is by doing File -> Save Copy of <package>.dtsx As ... from BIDS. When I did this, I had SSIS -> Package Configuration option checked.

    Next I run the package via SQL Agent. When I set up the step, I picked another configuration file, different from the one that was checked in BIDS, expecting the deployed package to use the values in this other config file. But when I run the Agent job, it is getting the value from the config file that was checked in BIDS, not the one that was picked in the SQL Agent Job.

    It seems in order for the Agent Job to use another config file is to redeploy the package after unchecking SSIS -> Package Configuration option.

    Is this the expected behavior?


    Wednesday, July 11, 2012 9:08 PM

Answers

  • It is an XML config file. I didn't consciously set anything for direct or indirect so probably the default type. So I guess that explains the  behavior.
    so that is direct configuration, and you should copy new xml configuration at exactly same physical address as you set in package development.

    http://www.rad.pasfu.com

    • Marked as answer by D00linDalton Thursday, July 12, 2012 7:38 PM
    Thursday, July 12, 2012 1:38 PM

All replies

  • what type of package configuration you used?

    is it xml configuration? sql configuration?

    is it direct or indirect?

    if you used Xml Configuration as Direct (which is default type), then you need to put new configuration file at the same physical address that you pointed at development time.


    http://www.rad.pasfu.com

    • Proposed as answer by Joon84 Thursday, July 12, 2012 7:49 AM
    Wednesday, July 11, 2012 9:43 PM
  • Check whether the connection string of config file is ser correctly?, if it is xml config file check the physical address.

    Thursday, July 12, 2012 3:10 AM
  • It is an XML config file. I didn't consciously set anything for direct or indirect so probably the default type. So I guess that explains the  behavior.
    Thursday, July 12, 2012 12:50 PM
  • It is an XML config file. I didn't consciously set anything for direct or indirect so probably the default type. So I guess that explains the  behavior.
    so that is direct configuration, and you should copy new xml configuration at exactly same physical address as you set in package development.

    http://www.rad.pasfu.com

    • Marked as answer by D00linDalton Thursday, July 12, 2012 7:38 PM
    Thursday, July 12, 2012 1:38 PM