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

Row Total In Table

Hi,
I have a table in my report (not a matrix) that displays 50 rows by
6 columns - fixed, no grouping requirements. The user wants to see the
total of both the vertical column (easy) and also the horizontal row - not
so easy.
First I tried this expression = SUM(Fields!Field1.Value +
Fields!Fields2.Value....etc) but this did not give the correct number.
A co-worker told me that a horizontal row sum was "impossible" to do
with a table and that I had to swap my table for a matrix.
Can anyone tell me how to get the sum of a horizontal row of a
table?
JDJust try this,
= SUM(Fields!Field1.Value +sum(Fields!Fields2.Value) + ....etc
Amarnath
"Joe Delphi" wrote:
> Hi,
> I have a table in my report (not a matrix) that displays 50 rows by
> 6 columns - fixed, no grouping requirements. The user wants to see the
> total of both the vertical column (easy) and also the horizontal row - not
> so easy.
> First I tried this expression = SUM(Fields!Field1.Value +
> Fields!Fields2.Value....etc) but this did not give the correct number.
> A co-worker told me that a horizontal row sum was "impossible" to do
> with a table and that I had to swap my table for a matrix.
> Can anyone tell me how to get the sum of a horizontal row of a
> table?
>
> JD
>
>|||Sorry, Sending you again
Just try this
= SUM(Fields!Field1.Value) + SUM(Fields!Fields2.Value) + ......etc
Amarnath
"Joe Delphi" wrote:
> Hi,
> I have a table in my report (not a matrix) that displays 50 rows by
> 6 columns - fixed, no grouping requirements. The user wants to see the
> total of both the vertical column (easy) and also the horizontal row - not
> so easy.
> First I tried this expression = SUM(Fields!Field1.Value +
> Fields!Fields2.Value....etc) but this did not give the correct number.
> A co-worker told me that a horizontal row sum was "impossible" to do
> with a table and that I had to swap my table for a matrix.
> Can anyone tell me how to get the sum of a horizontal row of a
> table?
>
> JD
>
>|||To get the horizontal row sume miss out the SUM(). Just use the expression
=Fields!Field1.Value+Fields!Field2.Value+...+Fields!Field6.Value
HTH,
Magendo_Man
"Joe Delphi" wrote:
> Hi,
> I have a table in my report (not a matrix) that displays 50 rows by
> 6 columns - fixed, no grouping requirements. The user wants to see the
> total of both the vertical column (easy) and also the horizontal row - not
> so easy.
> First I tried this expression = SUM(Fields!Field1.Value +
> Fields!Fields2.Value....etc) but this did not give the correct number.
> A co-worker told me that a horizontal row sum was "impossible" to do
> with a table and that I had to swap my table for a matrix.
> Can anyone tell me how to get the sum of a horizontal row of a
> table?
>
> JD
>
>

Row and column count in SSMS

When you execute an MDX query the Messages tab displays the number of rows and columns returned.

However, that includes the rows and columns used to hold the member names. Personally I would prefer it only returned the rows and columns in the cellset.

Anyone agree/disagree? Discuss!!!

Also, a minor point. I'd like it if the rows and columns were displayed on the results tab like the number of rows are in a SQL query. Anyone agree?

cheers

Jamie

Hi Jamie,

The row and column counts returned for empty axes are also a bit inconsistent :

>>

select {} on 0
from [Adventure Works]
-
Cell set consists of 1 rows and 0 columns.

-
select {} on 0,
{} on 1
from [Adventure Works]
-
Cell set consists of 0 rows and 0 columns.

>>

The separate Message Tab takes some getting used to, but it works OK for me...

|||

Interesting, thanks Deepak.

Anyone else?

Rounding error when summing 4 numbers to 0

When I sum the 4 numbers (-550.83, 1690.65, 550.83, -1690.65), it should add up to zero. It displays correctly to 2 decimal places. I know that they are stored internally as a double. However, I use the number as a denominator in a calculated member and the test for zero fails. I have to use bounds such as > -00000001 and <0.00000001. The result is a very large number in billions if the filter is not used in the calculation.

Has anyone come across this or got a better suggestion? I can also use the VBA round function.

Thanks

If these are always going to be decimal numbers, as in the example above, does the changing the data type to "Currency" help?

http://msdn2.microsoft.com/es-es/library/ms129408.aspx

>>

SQL Server 2005 Books Online

DataType Element (ASSL)

Defines the data type of the associated element.

...

The values for DataType are defined in the System.Data.OleDb.OleDbType enumeration. However, only the enumeration values in the following table are valid in the DataType element.

Value	Description
BigInt	A 64-bit signed integer. This data type maps to the Int64 data type in Microsoft .NET Framework and the DBTYPE_I8 data type in OLE DB.
Bool	A Boolean value. This data type maps to the Boolean data type in the .NET Framework and the DBTYPE_BOOL data type in OLE DB.
Currency	A currency value ranging from -263 (or -922,337,203,685,477.5808) to 263-1 (or +922,337,203,685,477.5807) with an accuracy to a ten-thousandth of a currency unit. This data type maps to the Decimal data type in the .NET Framework and the DBTYPE_CY data type in OLE DB.

...

>>

|||

Thanks for the info and a possible solution. I have to bring it in as a double.

The source fact table is in account dimension format with only one measure DECIMAL (24,12). The measure can be pounds shipped, gross sales, or some marketing dollar allocation to 12 places. If I used currency, I would lose significant precision due to rounding to 4 decimal places.

I think the structure of my client's source fact table is already determining how I manage this. I wish SSAS would allow you to set the source format such as DECIMAL (24,12). I have the calculated measure isolated in one area, but it may impact performance when the client drills down hierarchies. Here is the code I used for the calculated measure.

IIF(([Measures].[EXPENSE DTL AMT], [WATERFALL DIM].[Waterfall].&[1]) > -0.000000001 AND
([Measures].[EXPENSE DTL AMT], [WATERFALL DIM].[Waterfall].&[1]) < 0.000000001,
0, ([Measures].[EXPENSE DTL AMT], [WATERFALL DIM].[Waterfall].&[1]))