Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SQL_Rookie
Starting Member
32 Posts |
 Posted - 2008-09-11 : 09:36:43
|
| Can someone tell me what are the pros and cons of doing parent and child ackages?I think I want to implement this concept but I'm affraid it will increase the overhead and processing time. Here is my scenerioI have a pkg that would be calling 3 child pkgs. Each child pkg calls a web servie and retrieves an xml string. Each child pkg would be recieving variables from parent which are need to get query the web service. The reason I would like to do child pckgs is cause I want to create mutiple parent pkgs that would call the same set of 3 child pakgs. So if I have say 4 or 5 main pkgs and eash of those would call the same 3 child pkgs (cause the web service call would be doing the same thing just different data set or xml data coming from the web service since we pass different values to query.) would that work or would the child pkg be blocking each other and causing errors?? The main pakgs would be schedule to run every 15 minutes so that is 4-5 main pkgs running every 15 minutes which calls those child pkgs but those child pkgs are running in seperate process since they are fired from different main pkgs. |
|
|
|
|
|
Parent and Child packages?