Home Dashboard Directory Help
Search

SSIS 2012 Execute Package task: External Reference does not work with SSISDB by Marcel Franke


Status: 

Active


26
0
Sign in
to vote
Type: Suggestion
ID: 779789
Opened: 2/22/2013 4:21:43 AM
Access Restriction: Public
1
Workaround(s)
view

Description

There are currently two options within the Execute Package Task to execute child packages: Project Reference and External Reference. The problem with project reference is, that all packages need to be within the same SSIS projects. This is an issue for large projects, because it also affects the deployment. But when I switch to External Reference combined with SQL Server, I can not see the SSIS packages which are deployed in the new SSIS db, when I choose the SSIS DB as source.
Details
Sign in to post a comment.
Posted by SSISJoost on 6/20/2014 at 4:35 AM
This is a limitation! You often have a master project that executes packages from other projects (Staging, DWH, Datamart, etc). Like BI Monkey mentioned, it's not an option to have all these packages in one project. The only workaround I found was using a Script Task. It works, but a real solution would be much better.
Posted by BI Monkey on 5/29/2014 at 5:06 AM
This is as (other commentators note) an extreme limitation on the ability to use SSIS in a complex enterprise environment. You cannot have a central command and control system for hundreds (or thousands) of packages by having it all in one monstrous project.
Posted by Volvox77 on 3/17/2014 at 7:22 AM
I would have thought that Project Deployment was supposed to be the way for the future of SSIS. Seems like a rather questionable feature to advertise if it doesn't work with standard design patterns.
Posted by Imbastuff on 8/21/2013 at 10:21 PM
Can only agree.

It is very cumbersome, not to mention confusing, to need to create a Execute SQL-task to trigger a sp to run a package in SSISDB (http://msdn.microsoft.com/en-us/library/ff878160.aspx) when you'd like to execute package.
Posted by dline292 on 8/1/2013 at 10:11 PM
Now that the DTS functionality is back for passing parameters to child packages, it allows for easy building of SSIS frameworks with reusable child packages. But with the all or none deployment model, it is challenging to manage large projects with multiple developers, especially since the slightest change to any package in the project updates the project file. Because of this, it's easier to break up large project into smaller projects grouped by related packages. However, with this identified limitation, there is no way to reference the reusable child packages between projects.

SSIS 2012 made a huge leap forward towards making SSIS a serious contender in the ETL space, but this is a major limitation. Every effective developer utilizes centralized and reusable code, and the lack of this feature prohibits it. Please add this.
Posted by Olaf Krumnow on 6/5/2013 at 2:05 AM
Is there a workaround available? How can I start a task deployed to a server from another SSIS task?
Posted by Microsoft on 5/23/2013 at 1:06 PM
Hello Marcel. We’ve looked into this item. While it will not be addressed in the current release cycle, we have added it to a list for consideration for the next. Thank you for the feedback. We will keep track of the suggestion. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Sign in to post a workaround.
Posted by SSISJoost on 6/20/2014 at 4:29 AM
As a workaround you could use a Script Task with some .Net code to execute packages from an other project in the SSISDB. More details:
http://microsoft-ssis.blogspot.com/2014/06/ssis-2012-execute-package-task-external.html