• I've tried a few more things to no avail. I found another report that has a large dataset and ran them both a few times.

    Trouble report: Bytes Retrieved 30389 TimeDataretrieval 345631

    Second report: Bytes Retrieved 48770622 TimeDataretrieval 158468

    Our Vendor thinks it's our network but I don't. Not when a report on the same server gets 1000X the amount of data in a 3rd the amount of time.

    I've also gutted the report to remove all the formatting and just dump a few small text columns to a table with zero expressions on it. as Simple as I can get.

    I've checked the disk IO and it's fine. I'm about to look to see if things are paging, as I just noticed (why executionLog3 bothers with an XML column I don't know. Why not just make three or four more damn columns???) that them EstimatedmemoryUsageKB for the trouble report is 1,444,296. Another Ideas to look at would be greatly appreciated.

    Steve