closing pipelinebuffer

Hot Topic

RS 2005 connecting to Clustered sql 2000 server
Job fails for package containing Script Task with error "The script files failed to load."
where to place articles
Execute Package Task behavior
Some ideas for custom tasks/components
Databound image in report header
Web App Failover problem
Error 404 when opening reportserver
"Login Failed" for sqlcmd using integrated on Vista Beta 2
Forcing Users to log out of SQL 2000

SQL Server

RDA Pull Error table
SQL Server Memory Configuration share nicely with COM
Export Wizard generates errors
Web Synchronisation Using RMO
SQL 2005 Database Mirroring - AD required?
sp_denylogin
Reading and writing same variable to a script
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Calling normal stored procedures from Extended Procedures
Determine date Database was last used ?

closing pipelinebuffer

Is there a way to signal to the PipelineBuffer during ProcessInput that no more rows are necessary

Say I have a component's output connected to a custom destination component... in the destination component's properties, I can set the number of rows I want to consume.  (The first 50 rows for example.)  If I do it this way, the source component continues delivering rows - I can set my destination to ignore all rows after 50, but would like a way to tell the component above it "no more!"

Is this possible

Steve

Answer this question

closing pipelinebuffer

  • Viral Parikh

    Why not put in an extra transform component that only provides a certain number of rows. Like this: http://blogs.conchango.com/jamiethomson/archive/2005/07/27/1877.aspx

    -Jamie


  • Steve1234567

    Actually, that's exactly what I'm doing.  But what happens is that say I just want 10 rows, and the input has 1,000,000 rows... the input will continue sending all 1,000,000 rows, even though they're being ignored.  It would be nice to have something that tells the upstream component, "Hey, I don't need you anymore, don't send anything else, report success!"

  • notanotherusername

    I am not sure what effect it would have on the upstream component, probably none, but to signal you are adding now more rows in ProcessInput you would normally use buffer.SetEndOfRowSet()

  • C Shah

     Steven Pasetti wrote:
    Actually, that's exactly what I'm doing.  But what happens is that say I just want 10 rows, and the input has 1,000,000 rows... the input will continue sending all 1,000,000 rows, even though they're being ignored.  It would be nice to have something that tells the upstream component, "Hey, I don't need you anymore, don't send anything else, report success!"


    This will be helpful for debugging too... I can debug with only 10 rows and if everything is fine, I can run the 1,000,000 rows later. 
     


  • szevvy

    No, you can not signal upstream components that you are done processing.  You would have to do this at the source.

    Thanks,
    Matt

  • Fabriz

    Ahh.. I was looking at an asynch component, and have the output buffers being used in ProcessInput!

    I don't think this can be done, and not sure that it is a good idea even if you could. It would be like cancelling the package, mid-flow.

  • Mark Blackburn

    Tried this... Can't use buffer.SetEndOfRowSet() on an input buffer, it throws an exception.

    Also tried using buffer.Discard() but it seems to not have any effect on stopping the rows from continuing into the component.

    Steve
  • closing pipelinebuffer
Answer this question