locked
Report Rendering taking long time RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    I have a report builder report 3.0. This accesses a sql server table and has 100000 plus  records. I have 5 parameters and indices on the table. The query is taking less time but the report is taking forever to render. Please need help.

    Thanks

    Tuesday, February 9, 2016 6:23 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi PMunshi,

    Since you mention you have checked the execution log view, have you found which section costs most of time, TimeDataRetreval, TimeProcessing or TimeRendering?

    In your scenario, it seems that you have created cascading report parameters, right? Please check the dataset used for retrieving cascading parameter values, make sure it only return the useful field. When you run the report, please use SQL Profiler to monitor the query performance.

    Best regards,
    Qiuyun Yu 

    Qiuyun Yu
    TechNet Community Support


    Wednesday, February 24, 2016 9:23 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     For 100000 records it may take more time to render in the browser. Could you please explain bit more on exactly what you are trying to achieve with 100000 records ?  If you looking for downloading the data into different format like excel , you can consider using a subscription to get it delivered in email or shared folder.

    Best Regards Sorna

    Tuesday, February 9, 2016 7:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     For 100000 records it may take more time to render in the browser. Could you please explain bit more on exactly what you are trying to achieve with 100000 records ?  If you looking for downloading the data into different format like excel , you can consider using a subscription to get it delivered in email or shared folder.

    Best Regards Sorna

    Thanks Sorna. Some want to select few values from the drop down parameters and some users want to select All , that is when it is taking time
    Tuesday, February 9, 2016 7:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    ok now even after selecting parameters , for 3000 rows also its slowing down and throwing not enough storage error
    Tuesday, February 9, 2016 7:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi PMunshi,

    In Reporting Services, to troubleshoot the report performance issue, we need to check execution log view to find which section costs most time, TimeDataRetreval, TimeProcessing or TimeRendering. Please refer to this thread: SSRS Tabular Report is taking too much time to render.

    Regarding the not enough storage error, please check the Reporting Services error log (default location: %programfiles%\Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles) around the time that the error message thrown out. Also please reboot the computer and restart the SSRS service to see if the same issue occurs. Please refer to this thread:
    Report Builder 3.0 2008 R2 - Max Columns - Not Enough Storage

    If you have any question, please feel free to ask.

    Best regards,
    Qiuyun Yu

    Qiuyun Yu
    TechNet Community Support



    Friday, February 12, 2016 6:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Qiuyun Yu will do the same and post my findings. Also can you lease tell me how i can find if my Report builder 3.0 is a 32bit or 64 bit?

    Thanks


    • Edited by PMunshi Friday, February 12, 2016 2:52 PM
    Friday, February 12, 2016 2:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi PMunshi,

    In Reporting Services, to troubleshoot the report performance issue, we need to check execution log view to find which section costs most time, TimeDataRetreval, TimeProcessing or TimeRendering. Please refer to this thread: SSRS Tabular Report is taking too much time to render.

    Regarding the not enough storage error, please check the Reporting Services error log (default location: %programfiles%\Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles) around the time that the error message thrown out. Also please reboot the computer and restart the SSRS service to see if the same issue occurs. Please refer to this thread:
    Report Builder 3.0 2008 R2 - Max Columns - Not Enough Storage

    If you have any question, please feel free to ask.

    Best regards,
    Qiuyun Yu

    Qiuyun Yu
    TechNet Community Support



    Qiuyun Yu,

    I restarted the services and rebooted my machine and still there is no difference. I did run the following SQL to get the total time and rendering time

    SELECT l.*,r.*, TimeDataRetrieval+TimeProcessing+TimeRendering AS TotalTime,Format,Parameters,username,TimeStart 
FROM dbo.ExecutionLog L WITH (NOLOCK) INNER JOIN dbo.Catalog R WITH (NOLOCK) ON L.ReportID = R.ItemID 
where Name='CourtActivityReport'
 ORDER BY l.TimeStart desc

    The issue is i have 5 parameters and its taking long time to load the next parameter. For example when i choose "SelectAll" for the first parameter, its taking long time to populate the second parameter and so forth.

    Monday, February 15, 2016 2:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Qiuyun Yu will do the same and post my findings. Also can you lease tell me how i can find if my Report builder 3.0 is a 32bit or 64 bit?

    Thanks


    Hi PMunshi,

    Currently, already published report builder versions are X86.

    Best regards,
    Qiuyun Yu

    Qiuyun Yu
    TechNet Community Support



    Wednesday, February 24, 2016 9:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi PMunshi,

    Since you mention you have checked the execution log view, have you found which section costs most of time, TimeDataRetreval, TimeProcessing or TimeRendering?

    In your scenario, it seems that you have created cascading report parameters, right? Please check the dataset used for retrieving cascading parameter values, make sure it only return the useful field. When you run the report, please use SQL Profiler to monitor the query performance.

    Best regards,
    Qiuyun Yu 

    Qiuyun Yu
    TechNet Community Support


    Wednesday, February 24, 2016 9:23 AM