June 27, 2017 at 9:00 pm
My ssrs report takes more time sporadically, when I view the execution log it shows that it take more time for timeprocessing and timedataretrieval is always less.
I don't understand why timeprocessing is more sporadically, if it take more time always then I can work on timeprocessing parameter. any suggestion please.
June 28, 2017 at 3:55 am
Hi,
are there some other users on the reportserver or on the sql server, where the database is located?
Are there some jobs running via scheduler, if you try to get your report?
The tables for your report, have they always the same size, or from report to report different?
June 28, 2017 at 4:01 am
Just to chime in a little, is SSRS hosted on the same server as the SQL Server engine? If so, how much of the resources is SQL using? Is it leaving enough memory for SSRS to be able to have a decent amount? For example, if you have 32GB of RAM, and SQL Server is using 29(ish)GB of that, that leaves 3GB for everything else, including the OS. That's not going to give SSRS a lot of resources to render the report once you take other services running into account.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
June 29, 2017 at 4:49 am
Are the reports parameters vastly different and therefore returning varying data sets sizes. Such as a Date To and Date From parameter?
This would explain time processing. Or are you saying the same parameters are producing different processing times?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply