Parameter passing from SQL Server agent

  • Hi,

    Below is the scenario,

    •I'm calling the SSIS packages through SQL agent job. The packages have variables defined with default values.

    •The parent packages have no package configuration. The child packages have package configuration of ‘Parent Package variable’ type

    •The variables are being passed from the job.

    •The job calls the parent package which loops though the child packages

    I would like to know how the variables traverse through the packages and the jobs?

    Another doubt not related to above. I am unable to make any changes to the connections. Whatever changes I make it is getting reverted to the original if I click elsewhere. So as a workaround I view the code in XML and change. Can you please suggest if there are any properties to be changed?

    Cheers

    Jim

  • Jim1234 (6/11/2015)


    Hi,

    Below is the scenario,

    •I'm calling the SSIS packages through SQL agent job. The packages have variables defined with default values.

    •The parent packages have no package configuration. The child packages have package configuration of ‘Parent Package variable’ type

    •The variables are being passed from the job.

    •The job calls the parent package which loops though the child packages

    I would like to know how the variables traverse through the packages and the jobs?

    Another doubt not related to above. I am unable to make any changes to the connections. Whatever changes I make it is getting reverted to the original if I click elsewhere. So as a workaround I view the code in XML and change. Can you please suggest if there are any properties to be changed?

    Cheers

    Jim

    The parent package get its variables from the SQL Agent job, and the configuration you have specified in the child packages means that the child packages will get their variable values from the parent package. This blog post from Tim Mitchell may help: http://www.timmitchell.net/post/2014/06/26/ssis-parent-child-architecture-in-package-deployment-mode/

    The most likely reason for not being able to make persistent changes to your connections, is expressions. If an expression is used to set the connection string (or some elements of it), changing it in the designer will effectively not do anything as the expression will override it.

Viewing 2 posts - 1 through 1 (of 1 total)

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