ExecutionLog3 table in Reportserver Database

  • I have a SSRS report for which users are complaining to be slow, but from querystore, I can see that the SP (Report only has this SP execution) is taking less than 15sec. In ExecutionLog3 table, timedataretrieval for the same report is showing up to be for more than 20 mins.

    Could anyone tell me why is the data looking different in querystore vs Reporserver database. Does timedataretrieval accounts for anything else other than getting the data from database?

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • Hi,

    maybe there is a difference between collection the data, and displaying the data in the report.

    What kind of report do you use, pie  shart, table or something like that?

    Good luck,

    Andreas

  • Could be a rendering issue if you are doing any calculations, Conditional formating or grouping with totals in the report.  Or if you have a embedded image. Take a look at executionlog3 fields:

    Format: The rendering format used (e.g., PDF, Excel, HTML)

    TimeDataRetrieval:TimeDataRetrieval measures the time taken to fetch data from the data source(s) used in the report. It accounts for the execution of queries or stored procedures and the transfer of data to the SSRS server

    TimeProcessing:

    • Refers to the time spent processing the report data.
    • Includes activities like executing queries, applying filters, and aggregating data.

    • If this value is high, it often indicates inefficiencies in the dataset query or complex report logic.

    TimeRendering:

    • Refers to the time taken to render the processed data into the final output format (e.g., PDF, Excel, or HTML)
    • Includes activities like formatting, pagination, and applying styles.
    • High rendering times may be caused by complex layouts, heavy graphics, or large datasets.

     

     

     

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

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