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

Report doesn't run from Reporting Server Expand / Collapse
Author
Message
Posted Wednesday, March 6, 2013 8:18 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, December 12, 2014 1:20 AM
Points: 251, Visits: 927
Dear All,

I'm trying to run a Report on the Reporting Server but for some reason the reports executes but hangs. In Visual Studio, when the Report is run from the Dataset (right click on the Dataset-> Dataset Properties-> Query Designer-> execute the report) it works fine, but when I righ click on the actual report then select run the Report executs but it just hangs. I want to know what the cause of it could be please?

Thank you in advance!
Post #1427448
Posted Thursday, March 7, 2013 3:16 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 10:57 AM
Points: 2,112, Visits: 3,712
Typically that would indicate it's taking time to create and/or render the report. Are you getting an error or just the spinning wheel?
Leave it running until it times out & check the executionlog view in ReportServer database - it has fields TimeDataRetrieval, TimeProcessing, TimeRendering which can help you work out what's taking the time.
Post #1427869
Posted Friday, March 8, 2013 6:28 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 11:56 AM
Points: 317, Visits: 1,529
Sometimes when a report seems to run "forever" or timeout, the problem stems from either having an underlying query that is written as "Select * From...." -- Seems like SSRS report manager gets tripped up by the "*" once in awhile, especially if the underlying fields have changed.

Another issue that sometimes causes problems is parameter sniffing. If your query uses a stored procedure where reporting services passes a parameter value, you may be running into parameter sniffing. Plenty of articles on SSC about easily overcoming this type of problem.

Just my two cents.

--Pete



Post #1428551
Posted Friday, March 8, 2013 6:40 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, December 12, 2014 1:20 AM
Points: 251, Visits: 927
Thank you for your reply! Yes, the Reports runs but hungs for a very long time but eventually gets the data but my question is why would the Stored Procedure run quicker than the when running the Rport on the Server.
Post #1428553
Posted Friday, March 8, 2013 6:52 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 11:56 AM
Points: 317, Visits: 1,529
I wish I could tell you exactly why a report might be so much slower in report manager vs. BIDS, especially when the report is referencing a parameterized stored proc.

Nonetheless, based on my own experiences, when a report does run slow in report manager vs BIDS, I usually discover a parameter sniffing problem.

So, here are a couple of links to articles about overcoming parameter sniffing:

http://elegantcode.com/2008/05/17/sql-parameter-sniffing-and-what-to-do-about-it/

http://www.sqlservercentral.com/blogs/practicalsqldba/2012/06/25/sql-server-parameter-sniffing/

--Pete



Post #1428561
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse