UnionAll/Multicast BUG?

  • Hi everyone,

    I've experienced a very annoying SSIS problem today.

    I attached a jpg to demonstrate it. As you can see the UnionAll task has an input of 22 290 rows but puts out only 2 736. Afterwards the Multicast has only one real output and the OLE DB destination remains empty.

    Is it a bug in SSIS or just in my package?

    Any help or idea would be greatly appreciated!

    Thanks,

    MartinIsti

  • It's by design. Only every third row is allowed...

    Really though, the destination is applying back pressure. As the union all task is an async task, it can accept lots and lots of rows before actually spitting them out. If you waited for your package to finish, you will see all the numbers match up.

    Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!

  • one thing i noticed is that this package has not completed yet so you do not know how many records are being returned out of the union all transformation yet. the union all transformation will start to output records before it processes all of the records in its input.

    i think you need to wait for the package to complete processing before you can decipher exactly what is going on.

  • Thanks for the replies but I think the problem is elsewhere. The package is running for more than an hour without any error and keeping yellow without any sign of activity (even in Profiler).

    Now I'm restarting from scratch and it seems working 🙂

  • I really doubtit was a problem. Your destination was probably just slow or blocked. Possibly your source blocked (I cannot remember what the source was)

    Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!

  • You mentioned that, The package is running for more than an hour and you ran profiler as well..

    did you see any processID or SPID with -2 value in profiler?

    🙂

Viewing 6 posts - 1 through 5 (of 5 total)

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