January 12, 2016 at 1:07 pm
Greetings,
I've been trying to find an answer to this for a couple of days, but either it doesn't exist (unlikely), or I'm just not phrasing the question correctly (far more likely); so I thought I would try here before I waste any more time.
I'm in the beginning stages of developing a new EL (no transforms, so...) package and with an eye to maintainability I've parameterized and variablized the utter stuffing out of it, as appropriate.
The question I have is this: can the same package be executed by two (or more) different jobs, each with their own set of parameters that make them distinctly different? These jobs wouldn't start at the same time, but they're large loads, so it's very likely that they'd be running concurrently.
January 12, 2016 at 1:17 pm
N.B. (1/12/2016)
Greetings,I've been trying to find an answer to this for a couple of days, but either it doesn't exist (unlikely), or I'm just not phrasing the question correctly (far more likely); so I thought I would try here before I waste any more time.
I'm in the beginning stages of developing a new EL (no transforms, so...) package and with an eye to maintainability I've parameterized and variablized the utter stuffing out of it, as appropriate.
The question I have is this: can the same package be executed by two (or more) different jobs, each with their own set of parameters that make them distinctly different? These jobs wouldn't start at the same time, but they're large loads, so it's very likely that they'd be running concurrently.
I believe you should be able to run multiple instances of the same package concurrently, as long as they don't interfere with each other trying to use/connect to any external resources. Internal resources such as variables and parameters for each instances should be independent from each other.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
January 12, 2016 at 1:28 pm
Alvin Ramard (1/12/2016)
I believe you should be able to run multiple instances of the same package concurrently, as long as they don't interfere with each other trying to use/connect to any external resources. Internal resources such as variables and parameters for each instances should be independent from each other.
The way I see this being set up is roughly:
1 Parent/Control Package
60 Child Packages (one for each source table)
The Job would supply the source user/pw as well as the destination schema. The current process (4 Parent/Control packages + 60 (x 4!) child packages) has logic already integrated that checks a control table before attempting to load a table to ensure it's not marked as in progress. There have been some issues in the past with specific timing, but we've worked around it so far by building a delay - I'm sure there's a better way, but I just haven't figured it out yet.
Right now it's a nightmare for me to maintain if a source table changes (columns, datatype, length, etc.) as I have to remember to update all four copies of the child package; same goes for making any performance or logging improvements - I have to duplicate the changes x 4.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply