SSRS vs. T-SQL - Query Response Time

  • I've found a way to avoid all performance problems associated with SSRS...

    ... avoid the use of SSRS. 😉

    --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)

  • I have the exact same problem stored proc 19 second SSRS version unig same parameters 40 + minutes and still going. Anyone have a solution for this SSRS bug?

  • You can check execution log for report and compare timerendering vs timedataretrieval. It could be poorly designed report that takes a lot of time to render.

  • @Dream, any resolution?

  • Add the OPTION (OPTIMIZE FOR UNKNOWN)

  • dreamornightmare1 (7/9/2012)


    I have the exact same problem stored proc 19 second SSRS version unig same parameters 40 + minutes and still going. Anyone have a solution for this SSRS bug?

    Is your SSRS calling that same stored procedure or did you try to do it all in SSRS by itself?

    --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 6 posts - 31 through 36 (of 36 total)

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