Configuration

  • Hi ,

    I have around 50 Entities.Where in for each entity I have around 6-20 Packges .In each package Iam calling a configuration Script Where all the parameters for the Procedures ,DB Connections are configured.

    So no of configuration scripts =40[No of Entities] * 6[No of Packges]=240 Times (mininum)

    Where in I have to run all these 40 entities to 7 countries .

    For every country I have a seperate DB .Connection to DB is Fetched Using Package Name

    .Through this Packge Name there is a global table where we fetch data for each country.

    So I need to rename all 240 Packges for evry country .For All this entities we wil Create Seperate Jobs for

    each of country in SQL Agent .

    Its too cumbersome.Kindly request you to provide an alternative solution to avoid this renaming of packages and config script calls and easy deployment.

  • One parent package with a For Each loop that gathers all the appropriate configuration parameter values and passes them to a single child package that takes the configuration parameter values and does the actual load work. If you can't figure out how to make a single child package do all the work, you can use several child packages and call the appropriate one based on the configuration parameter values.

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

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