• FridayNightGiant (6/21/2016)


    If you have 3 datasets embedded in your report and they each return 100 rows then the row count in the execution log should display 300. If the datasets are shared then you will see them as separate entries in the execution log with their own row counts.

    Remember the datasets could return 6000 rows but the report only display 1 row due to filters and groupings. I would double check the stored procedures to ensure there is nothing that could return more rows than expected.

    The first thing I did was go through the procs to make sure they were all returning what they should be and they were all behaving. There is a bit of witchcraft done to remove duplicates and create legible sentences but nothing that should hide 600000 rows.

    I see what you mean about the row count showing the sum of the datatsets but even allowing for that it seems extremely high. It looks more like a Cartesian product of the row counts. I can see how that could get high quickly, particularly if there's a couple of datasets returning 100 + rows.


    On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" ... I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
    —Charles Babbage, Passages from the Life of a Philosopher

    How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537