CODEWITHSUNDEEP
ssis
Alapan Bag
Alapan Bag

Reputation: 265

Is there any alternative to creating Parent Package variable in SSIS?

I have three SSIS solutions each containing around 50 packages each. Each package has got a Master package where the Server name is hard coded and this variable is called by the child packages of respective solution. The Master package of each solution is called by a job. And of course, it is of Package Deployment model.

This was working fine when it was in 2008 version but lately after migrating to 2017 the child packages are unable to get the variable which it was supposed to fetch from the parent package and as a result the job is failing. I have hard coded the server name in each of the variables of each package for one solution and it worked. But it is not possible to hard code for the all the packages of all the solutions.

So my question is there any other way I can make it work? Convert to project deployment model? or any other less time consuming solution?

Keep in mind I have just mentioned about one such variable but in reality there are other variables present there too which serves the same purpose. The number of such variables vary from solution to solution according to their need.

Thanks in advance

Upvotes: 1

Views: 98

Answers (1)

Ferdipux
Ferdipux

Reputation: 5246

You can migrate to Project Model. Advantages of this approach:

  1. Calling packages from the same project is straightforward - all you need to specify the package name in the project.
  2. All packages can share Project parameters, which are read-only variables available in all packages. You can set project parameters at Master package start, or configure it to be copied from SSIS Environment Variables.

Project Mode is a good step forward compared to Configs of SSIS 2008 packages. The only downside -- Execute Package task calls packages from the same Project without trouble. Starting packages from other Projects (Project other than that of calling package) is not that straightforward and you have to do some tricks.

SSIS Environments allow to maintain configurations, with server names, connection strings etc specific to your environment. For example, task of maintaining Dev, QA and Prod environment settings is much easier with it than with old good Config files.

Upvotes: 2

Related Questions