Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSRS 2008 R2 Report Query Generating ASYNC_NETWORK_IO Expand / Collapse
Author
Message
Posted Wednesday, October 16, 2013 7:14 AM


UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: 2 days ago @ 8:43 AM
Points: 1,434, Visits: 721
Hello all,

I have an issue with my report server in that it is struggling to process reports with large datasets. Whenever I run the report in question from a client it just runs and runs and runs with no sign of completing. The ReportingServicesService.exe uses up 100% CPU of a given processor and will just wait until I kill the query on the SQL Server.

If I run the query against the database in Management Studio itself it completes within a couple of seconds and returns over 80,000 rows. I can't do any more optimisations in terms of indexes etc. If I run the report and look at the wait stats I'm getting an ASYNC_NETWORK_IO WAIT being reported and very little in the way of impact on the actual server itself.

I've even tried running the report on the server itself to rule out any network latency issues, but I still get the same wait type on the query.

Any thoughts?
Post #1505174
Posted Monday, October 28, 2013 3:34 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, June 9, 2014 6:02 AM
Points: 2,674, Visits: 697
It's all a bit vague really! I have constant issues with SSRS (large) reports. I'm thinking likely an issue with the rendering - you don't say in which format you're outputting the report, have you tried changing this?
In no particular order I'd suggest you hunt out all the various logs to see if you can get a clue there. You could try rebuilding indexes etc. in the various databases including the tempdb and reportserver tempdb and/or update stats etc.
the async network may indicate an issue communicating with the client e.g. potential latency - however if the report pages then it may mean nothing.
Try limiting the result set until the report renders, try 10k rows, less if required.
about the best I can offer to be honest


The GrumpyOldDBA
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Post #1509126
Posted Monday, October 28, 2013 3:53 PM


UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: 2 days ago @ 8:43 AM
Points: 1,434, Visits: 721
Thanks for the reply. The issue seems to be around the report rendering somehow (all I'm doing is running the report in report manager). I can use the same dataset in a new report with just one table and the report runs fine. The report I'm having issues with is using some distinct values from the dataset and displaying it elsewhere in the report, so I'm just going to re-write it.

Thanks again!
Post #1509133
Posted Monday, October 28, 2013 3:57 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, June 9, 2014 6:02 AM
Points: 2,674, Visits: 697
no worries .. trying to figure out poor performing SSRS seems to be a very black art!

The GrumpyOldDBA
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Post #1509134
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse