Why you can't set up in 'disabled status' a task in Data Flow layer???

Why you can't set up in 'disabled status' a task in Data Flow layer???

• Martin Cowen

  its worth my mentioning my favourite 3rd party component here - the Trash Destination. http://www.sqlis.com/default.aspx 56

  It terminates your data-paths without putting the data anywhere. Very useful for debugging!

  -Jamie

  
  
  

• Nbraun77

  Data Flow objects behave quite differently from Control Flow objects - disabling a transform may invalidate much that happens downstream. This is especially the case for asynchronous components. I can see cases where disabling synchronous components could be useful, and indeed I have some ideas around how that might be done in the future.

  I would be interested to hear more about your scenarios and reasons for asking about this. Or perhaps you were just asking (no harm in that of course)

  Donald

  
  
  

• Morgan Schwertfeger

  Do you mean a script component They certainly can have a lot of code in them.

  What I do is this ...

  I create a package variable that can hold a boolean value, or sometimes an integer.

  In my script I put If ... Then ... Else constructs round blocks of the code I may want to disable. I can then switch the code on or off using the variable. (I use an integer variable so that I can switch multiple blocks of my script.)

  Once tested, you can comment out the If ... Then ... Else contructs to slightly improve performance - or you could just leave them there.

  Donald

  
  
  

• MBD-Team

  enric12879 wrote:

  hi Jamie, File System Watcher and Trash destination tasks seems very interesting but I wonder if they are enoughly safe in a production environment.

  Knowing the talents of the guys that wrote them I would say that you won't have any problems. Of course, I recommend you test it, just as you should any component, regardless of whether or not it comes out-of-the-box.

  One other thing, I can't think of any possible reason why you would use the Trash Destination adapter in a production environment. It is intended solely as a debugging aid.

  -Jamie

  
  
  

• Joshua Yates

  When you design a package you do a lot of tests and sometimes you need disable not delete any task which have a lot of code inside and then launch the whole package.
  
  

• AVNIP

  hi Jamie,

  File System Watcher and Trash destination tasks seems very interesting but I wonder if they are enoughly safe in a production environment.

  
  
  

• ksilhol

  One thing more... Aren't such task .Net assemblies I mean, done with Vb .Net or c#

  I had some old DTS which take advantatge of DLL (Customize tasks) written with Visual Basic 6.0. You can register and unregister and bla,bla.

  Is this the same I think so, or not

  
  
  

• Sundaraguru

  enric12879 wrote:

  One thing more... Aren't such task .Net assemblies I mean, done with Vb .Net or c# I had some old DTS which take advantatge of DLL (Customize tasks) written with Visual Basic 6.0. You can register and unregister and bla,bla. Is this the same I think so, or not

  Custom Tasks (and components) are indeed .Net assemblies.

  So yes, very similar to your COM DLLs for DTS.

  -Jamie

  
  
  
• Why you can't set up in 'disabled status' a task in Data Flow layer???