execution package task-SOS

hello to every body.. well i have a problem.. well i created a package the task of which is to update thedimensions and the fact tables from the tables of source.

i created a configuration file with all the parameters that are nedded (connections managers; parameters of packages).this config file will include all the paremeters need for the execution of other packages

In that package i call an other package (execution package task). this package normally will take the parameters of the parent package isn't it?(i put the parameters of this package to the config file of the parent package).

i must also note that for the second package called there is also a package...

i must also note that i have 2 DWHs (a and b) for testing.

the problem is that when i execute the parent package to DWH b , the sacond package called do not take the parameters of the parent package. instaed it looks to its XML configuration file(in a different location of the config file of the parent package) which contains the connection parameters to DWH a and it calls strored procedures from the DWH a (instead of calling at SP from DHW b).

any ideas?

thnx a LOT0

kats wrote:

The problem is that when i execute the parent package to DWH b , the sacond package called do not take the parameters of the parent package. instaed it looks to its XML configuration file(in a different location of the config file of the parent package) which contains the connection parameters to DWH a and it calls strored procedures from the DWH a (instead of calling at SP from DHW b).

Does this mean you are using 2 different set of configuration against the same properties in the child package? It sounds to me like the child package uses 1 set to get configuration values from parent package variables and another one to get configuration values from a config file?

Perhaps, I do not understand your problem.

|||

well the truth is that the child package is used sometimes by itshelf(so it needs one config file) and some times is called by a parents package.

i created also the parent variables in the child package.

|||

In that case, i would pass the runtime variables values to the package from the sql agent job Values tab, this can be different depending the calling job or the server, I would keep the config file to hold only server and connections specifics and use network aliases to resolve to the correct machine according to the target box.

Philippe