Rowcounts don't appear

[reposted from the beta NG]

Hi,
I have a data-flow that, when I run it in the designer on its own, displays rowcounts in the GUI as data flows through the pipeline - as we would expect.

However, if I execute the package from another package (still from the designer), the rowcounts don't show anymore. Everything goes green/yellow/red as normal - just no rowcounts.

This is on IDW14. Haven't yet got IDW15 up and running.

Note that on the NG, Evan Black has confirmed he is seeing the same behaviour.

Regards
JamieHi,
I just want to reiterate the importance of this.

I am currently running a package that has so far been running for 2 hours. It is incredibly annoying that I cannot see how far through the execution it actually is.
I don't know what is going on with my package. All I know is that it is doing something thanks to task manager and the fact that, through Profiler, I can see it executing queries against SQL Server (because it contains a LOOKUP component).

I am trying to see if a change that I have made has made the package quicker or slower than yesterday. If I was able to to see rowcounts in the GUI I would be able to make a manual check of the throughput of the package. As it stands I can't do this and I'm pretty narked about it to say the least!

-Jamie|||With the Feb. CTP, I reported that I seemed to have a choice, when executing one DTS package from another, as to which dtsx package (of target) to target -- because each package has two dtsx files, one in the source directory and one in the bin directory:
#1)
Point the target of the connection at the dtsx package in the bin subdirectory
Advantage: Get coloring and everything when target is executed from caller
Disadvantage: Opens a new dtsx window in IDE, and if you edit it, all changes
will be silently discarded
#2)
Point the target of the connection at the dtsx package in the source directory
Advantage: (avoids disadvantage above, which leads to losing work and cursing)
Disadvantage: no coloring, so you wind up watching a screen where nothing happens for a long while, hoping that good things are really happening

This sounds somewhat related to what you're reporting.
|||Thanks Perry,
I always point at the version that ISN'T in the bin directory because as you say, any changes will be lost. Hence you should never point at the version in the bin directory. It is used by the runtime engine I think and should not be used by the developer.

I'm using the latest CTP. Colouring does occur when a package is executed from a parent, although not as readily as if a package is executed on its own. And we certainly don't get rowcounts.

So yes, this is a related issue. If I were you though I wuld not be touching the file in the bin directory!

-Jamiesql