Post reply

SSRS Reports RUnnine very slow

  • May 2, 2012 at 9:33 am

    #255729

    Hey guys

    any idea or what steps to take if Reports suddenly starts running slow...

    Before it was taking less than one minute but now its taking 5 to 8 min to complete.

    Any idea or guess where to start to improve ?

    Thanks

  • May 11, 2012 at 6:10 pm

    #1486681

    Are all other reports are running slow? If so then stop and restart Reporting Services.

    Are all the other reports running okay? If so

    Run the query or stored procedure to determine if the problem is there. If the query or proc run slow then troublesoot or tune the query/proc. Sometimes it's a data issue that isn't throwing an error. If the query/proc run fine then check to see if the proc had been altered recently. If so, drop and recreate the proc and run the report.

    If the above does not fix the report, then run the report with a very small date range. If it runs slow, then something is probably wrong with the report. Double check the Data Source Connection to be sure it is working. Assuming no changes have been made to the report recently, try re-deploying, make a copy, etc. If those don't help then it could be corrupt. Also, try reverting back to a previous version of the report if one available.

  • May 12, 2012 at 10:35 am

    #1486771

    logicinside22 (5/2/2012)

    Hey guys

    any idea or what steps to take if Reports suddenly starts running slow...

    Before it was taking less than one minute but now its taking 5 to 8 min to complete.

    Any idea or guess where to start to improve ?

    Thanks

    I'd first investigate the 2 usual suspects on such as thing... Parameter Sniffing and Page Life Expectancy (PLE).

    Also, if reports are taking "less than a minute" instead of occuring in seconds (usually something less than 5 for big reports is my personal goal), it's also likely the reports need some redaction for performance.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply