From your description it sounds like you are only needing to deliver summarized data per County and the user is not drilling into that for details.
If they need to drill into it it may not be worth it as you would need sub-reports to accomplish the detail row display.
If they don't drill into the data you could likely remove all the RTs and do all of your summarizations in SQL using a groupings.
RTs can really drag the performance down and with that many records and lot of RTs you could see drastic improvemetn in execution time by moving all the calculation onto the server and off the machine executing the report. Some people do not understand how the grouping and summary functions work and use RTs where they are not needed because they are comfortable with them but they are less efficient.
Maybe not worth it but since you are trouble shooting an issue you might consider if this is the right time for an overall improvement.
I also would not assume that the RTs are even necessary. Since you did not design it, it might be worth seeing if they can be replaced with summary functions which again would move that to the server side.
As for the 0's have you ever run this for a full 12 months before this month? I have a guess that the RT evaluation formula is using some sort of datediff and they missed the mark on the reset process with a month count, or some permutation of this concept.
Edited by DBlank - 05 Dec 2014 at 4:22am
IP Logged
