SSIS - Add Enable/Disable within Data Flow Tab - by test1212

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 410210 Comments
Status Closed Workarounds
Type Suggestion Repros 4
Opened 2/2/2009 1:12:18 PM
Access Restriction Public


Currently in the control flow we have the option to enable or disable any component.  It would be very handy to be able to do the same (or very similar) inside the data flow tab for when we have a number of different data flow streams and want to do testing or debugging without actually deleting the data flow steps that you don’t want to run.  
Sign in to post a comment.
Posted by Stewa11 on 1/12/2017 at 8:34 AM
scratch my previous comment a few minutes ago. It is possible to disable tasks inside a dataflow by using the conditional split. see my workaround
Posted by Stewa11 on 1/12/2017 at 7:54 AM
Can disable Data Flows at Control Flow level BUT I only want to continue the dataflow if a Parameter ''DeleteForDay" is = 1 and disable the dataflow task is "DeleteForDay" is !=
Conditional split works on data (eg country column = Germany). Can we have something that splits based on a Package or User Parameter? perhaps extend the conditional split? Maybe case on data or variables.

Mucho thanks
Posted by Johnma1 on 9/19/2014 at 6:24 AM
Yes this would be really handy when doing development or debugging.
Posted by Peter_D503 on 11/15/2012 at 8:12 PM
This should be included. How do I test a subset of functionality? How do I narrow-down an issue...
Posted by Derek Robinson on 5/9/2012 at 5:58 AM
I totally agree with the OP. It is a vital part of development and testing to include/exclude certain branches. recreating the components is a waste of time and error prone when all you want is for SSIS to ignore them as it does at Control Flow level.
Show me a programming language or IDE where you can't comment something out.
Posted by Microsoft on 7/23/2010 at 4:29 PM
Thank you for contacting us. After analyzing this issue and prioritizing it in the context of our current development plans, we have found regretfully that it does not meet the bar to be included in an upcoming product release. If you feel that you could provide us with more data to change that judgment, we welcome any further information. Your feedback continues to be invaluable to us and we take all your communication seriously. Please continue to contact us with any questions, suggestions and issues as they arise.

     The SSIS Team
Posted by Siddharth Mehta on 8/3/2009 at 4:55 AM
I do agree that this is a genuine requirement. For ex. If I need to DISABLE a particular component for example a Merge Join component which is in mid of a set of transformations, using expression would not help me with it. I would have to programatically find some solution using a script task which is also not a sure shot workaround. Disable functionality is required to disable individual components so that step by step and component by component testing can be done, also this will enable to suspend a piece of logic as a history maintenance instead of changing logic or adding external logic just to disable individual components.

Posted by Microsoft on 6/29/2009 at 2:18 PM
Thank you for your submission. We will be reviewing your information and providing you feedback on our findings and progress. Thanks for your interest and support of SSIS.