'Execute Package Task' - explain steps to implement

  • Hi,

    Can anyone help me by giving detailed step-by-step instructions for using the 'Execute Package Task'.

    Thanks!

  • Hey There,

    It's pretty straight forward.

    Drag the task into your package and link via the correct precedents if needed.

    Right click the Task and choose Edit.

    Under the General give it a name

    Under the Package Tab set the following

    Location:

    1.) The Name of the SQL Server running SSIS Service where the packages have been deployed too.

    2.) The location on the file system where the package has been stored. A note for this one...If you are running from the file system you need to ensure that what ever account your going to execute the package your calling this other package from has access to the directory where the package your calling exists. I know that's a whole lot..bottom line. The package your adding this task to needs to be able to access the directory where the package exists. When your executing in VS 2005 it's using your windows account to get access. If you run as a schedule task or via SQL Agent the account those services use will be used to get access.

    3.) Select the package name

    4.) If you assigned a password then you would enter it here. Otherwise leave as is.

    5.) Execute out of Process is mainly for performance. If you set it to true the other package will launch independant of the current package. Meaning if you look at the running process on the server you will DTS running twice instead of just once (will also create it's own threads. If you have set limits on the threads your intial package and you leave this set to false it can result in a slow down. Generally not an issue on small packages, but if they are large and resource intensive breaking the apart can be useful for peformance.

    The Expressions tab is there if you want to set these values dynamically on the fly using variables.

    That's all there is to it.

    From there you need to provide all the connection information.

    Enter the name of your SQL Server which is running the SSIS Service, and contains the package you want to run.

  • 🙂 thanks sooo much!

  • I have an Execute Package Task where the field Package Name is empty. Are there any situations where this field can be empty? This task needs to know which package to execute right?

    On our production server, there is a DTS package that has an Execute Package Task where the Package Name is empty. Strange. Could it be that the package name is in a global variable? If yes, how can I see where it is being set?

    DTS Newbie...

  • Maybe it's set by an Expression. Check the Expressions/Package Name property.


  • What is the location where your packages are stored: SQL Server or File system?

    If it is File system, then it is normal that the PackageName is not filled in. The task gets all te information it needs from the connection.

    Regards,

    Willem
    http://wschampheleer.wordpress.com[/url]

  • I have a execute package task but although it appears to run it does notdo anything. The package I am calling has a sequence container which contains an execute sql task, this populates package variables with ftp settings which are stored on the server, it then runs a script task which uploads the files.

    When I run the package from the start it gets to the execute package task, that package appears in the designer, it appears to go through the steps yet nothing is uploaded. When I open the second package and execute the sequence container the files are uploaded fine.

  • Sorted variable problem

  • Hi,

    I have a parent package with 2 execute packages tasks that are connected through a "success"contraint. Execute SSIS package 2 should not run until execute ssis package 1 is finish running successfully.

    however, when I ran the parent package, it seems that is executes the package 2 even if package 1 is not yet done.

    any thoughts?

    Thanks a lot for the help!

  • quasar_phoenicis (5/31/2011)


    Hi,

    I have a parent package with 2 execute packages tasks that are connected through a "success"contraint. Execute SSIS package 2 should not run until execute ssis package 1 is finish running successfully.

    however, when I ran the parent package, it seems that is executes the package 2 even if package 1 is not yet done.

    any thoughts?

    Thanks a lot for the help!

    Can you give a screenshot of the control flow layout?

    In the precedence constraints editors, check if you are using logical AND or logical OR.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • I would try putting package 1 in a sequence container and then adding the constraint from that to package 2.


  • Koen Verbeeck (5/31/2011)


    quasar_phoenicis (5/31/2011)


    Hi,

    I have a parent package with 2 execute packages tasks that are connected through a "success"contraint. Execute SSIS package 2 should not run until execute ssis package 1 is finish running successfully.

    however, when I ran the parent package, it seems that is executes the package 2 even if package 1 is not yet done.

    any thoughts?

    Thanks a lot for the help!

    Can you give a screenshot of the control flow layout?

    In the precedence constraints editors, check if you are using logical AND or logical OR.

    There's another connector to the execute package task and they're using OR. This is the main culprit.

    thanks a lot!

  • quasar_phoenicis (6/2/2011)


    Koen Verbeeck (5/31/2011)


    quasar_phoenicis (5/31/2011)


    Hi,

    I have a parent package with 2 execute packages tasks that are connected through a "success"contraint. Execute SSIS package 2 should not run until execute ssis package 1 is finish running successfully.

    however, when I ran the parent package, it seems that is executes the package 2 even if package 1 is not yet done.

    any thoughts?

    Thanks a lot for the help!

    Can you give a screenshot of the control flow layout?

    In the precedence constraints editors, check if you are using logical AND or logical OR.

    There's another connector to the execute package task and they're using OR. This is the main culprit.

    thanks a lot!

    Thanks for posting back. That was an important piece of information which should have been included in your original post, as I am sure you realise now.


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

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