Answered by:
How to call package with in package ?

Question
-
Hi All,
Actually, i have 5 different SSIS Packages. Now, third party tool will be inserting a record in mysql database for the packages to be run. Now, i need to schedule a package to run every 5mins to check whether any record get insert into the table with some status = "Open" and based on the that i need to trigger pack1, or pack2 or pack3.
Since, i am working for many technolgy i am not much familiar with SSIS. If some one help me giving tips or tools or code will be helpful
GubsThursday, October 15, 2009 8:21 PM
Answers
-
As mentioned above by the moderator, You can use SQL Agent job to handle to kick the package to run every 5 mins. Inside your package itself -you can create a master package to call all child packages (all 3 packages that you've metioned) using execute package task from the toolbox. In the pipeline, you can double click
your constraint or expression and apply rules if necessary.
hth,
Rok- Proposed as answer by rok1 Thursday, October 15, 2009 9:31 PM
- Unproposed as answer by Todd McDermid Thursday, October 15, 2009 9:37 PM
- Proposed as answer by Eric Wisdahl Friday, October 16, 2009 3:03 AM
- Marked as answer by gubs Tuesday, October 27, 2009 8:12 PM
Thursday, October 15, 2009 9:28 PM
All replies
-
You could use several SQL Agent jobs to handle this. Have each one run every five minutes, running your specific package. You can have a preceding job step check to see if the correct conditions exist before you attempt to launch the package, OR you can have the package check those conditions itself.
Thursday, October 15, 2009 8:32 PM -
As mentioned above by the moderator, You can use SQL Agent job to handle to kick the package to run every 5 mins. Inside your package itself -you can create a master package to call all child packages (all 3 packages that you've metioned) using execute package task from the toolbox. In the pipeline, you can double click
your constraint or expression and apply rules if necessary.
hth,
Rok- Proposed as answer by rok1 Thursday, October 15, 2009 9:31 PM
- Unproposed as answer by Todd McDermid Thursday, October 15, 2009 9:37 PM
- Proposed as answer by Eric Wisdahl Friday, October 16, 2009 3:03 AM
- Marked as answer by gubs Tuesday, October 27, 2009 8:12 PM
Thursday, October 15, 2009 9:28 PM -
hello Todd,
What part of my answer didn't meet your expectation? I would appreciate if you can clarify?
thanks,
RokThursday, October 15, 2009 9:44 PM -
No offense intended - but since you asked, there are some unwritten guidelines we like to see used. Just about every response to a post can be considered a "possible answer" - and the person who posted the response is very likely to think that their response is the correct answer, just as you did. You'll note that my response was quite similar and I could just have easily proposed it as the answer, but I didn't. (In fact, as a moderator, I could have marked it as an Answer outright.) If every responder marked their own post as a potential answer, then the value of that mark is eliminated - it begins to mean nothing.
We would rather that you leave your own posts as-is. The fact that you replied with a recommendation to the poster implies that you think this will solve their problem. Proposing your own reply as an answer is redundant.
But please feel free to mark other replies as possible answers - but do so sparingly. Only mark posts that you believe contain the complete answers. If there are posts in a thread that are helpful, but don't propose a complete answer (in your opinion) then you can vote them as helpful. Marking another poster's response as a possible answer indicates to the original poster that (at least) two people think this will solve his/her problem. That's where I see the real value in the "Propose as Answer" mark.
Yes - in some cases this will leave a thread with multiple good possible answers with none of them marked as "proposed answers". In my view - no harm done there - every response is almost inherently an attempt to answer the OP's query.
Again - no offense intended. Thanks for frequenting the forum and offering advice - everyone here appreciates it. Come back often!
Thursday, October 15, 2009 10:01 PM -
Thanks for sharing the unwritten guidelines.
RokThursday, October 15, 2009 10:21 PM -
Thursday, October 15, 2009 11:16 PM