"DTS.Pipeline" Warning Message in Progress tab of SSIS

  • I receive two warning messages when I execute a particular data flow that "the output column is not subsequently used... removing this unused column can increase performance"...

    "can"?  seems to me that it will break the task.

    In a dataflow you cannot use an OLE-DB component without a source, and the source has a query, for me it is "select stageFlag from tblTrans where stageFlag is null"... and the OLE-DB component updates the resulting rows stageFlag to 1 (true).

    How can I update the stageFlag without having selected something?  or am I totally missing something here?


    Cheers,

    david russell

  • David,

    Why not just use an Execute SQL Task with the query:

    UPDATE tblTrans SET stageFlag = TRUE WHERE stageFlag IS NULL

    ???

    Does that work for you?

    -Jamie

     

  • duh!  of course that works.  How simple.  Thank you Jamie.


    Cheers,

    david russell

  • okay, now I remember the reason why this was NOT the solution.  We only want to execute this on successful completion of the previous task... not just "completion" was either success or failure.  I had converted it as you suggested; but have now changed it back.


    Cheers,

    david russell

  • You've lost me. What is the difference between:

    "We only want to execute this on successful completion of the previous task"

    and

    "not just completion was either success or failure"

    ???

     

    -Jamie

     

     

  • If the prior operation fails we do not want to update the stageFlag... only when the operation was successful do we want to do so.  Doing as you suggested, the stageFlag would be updated even if we disabled the previous control flow component.  There is only a success flow into the new component you suggested - and success is defined as the previous component having completed, not necessarily having completed successfully.


    Cheers,

    david russell

  • Hang on, I'm lost.You say there are no OnSuccess constraints. Not only is it there - its the default.

    You are talking about control-flow right?

    -Jamie

     

  • We ONLY want the task to execute WHEN the proceeding task was successful, not regardless of....

     

    Thanks for the tips though, I do appreciate them.  This one is satisfactorily taken care of now.


    Cheers,

    david russell

  • This response was intended for another message from you... must have been one of those quantum moments you hear about; but there was something else on the screen when I replied to the message from you that appears above.  At any rate, doing the update your way resulted in rows being updated in the control flow even when they had failed (and thrown errors into a flat file destination) in the data flow.  I returned to doing things the way I was doing them before and it works as expected.  Now, I really must get off the forums and back into my own head a bit... 81 working hours until a major deliverable... thanks again Jamie.  I do appreciate you very much.  David


    Cheers,

    david russell

  • No problem. The reason you read something that isn't there anymore is cos I misread your original post and wrote something that didn't make sense - so I got rid of it.

    -Jamie

     

Viewing 10 posts - 1 through 9 (of 9 total)

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