I have a small report in SSRS 2016 that retrieves Applied Payment Information from DynamicsGP by Voucher, and it parameterized. I am attempting to embed this report with parameters into another application so that users in the other browser-based
application can view payment information on vouchers that originate in that application and are integrated into GP.
The technical implementation works in general. However, this type of information, while important, will be used randomly and sometimes the report may only run once a day, or not at all. The requirements are driven by Vendor inquiries to the local
AP staff.
I have found horrendous performance on start up. I have tried every trick in the book with regard to running the report on schedule, waking up SSRS by browsing to the site, cycling the app pools, launching IE with a script, etc. and
NOTHING makes the report wake up well.
I have found that if I browse to the report and run it with parameters for the first time in the morning using Report Manager, the initial performance is as horrendous as when it is embedded
If I run it once during the day through Report Manager and then use it inside the embedded application, the performance consistently stays good throughout the day, no matter how long I wait after the initial run. It just seems that no matter what I
do, it will have to be run once before it performs well.
This is not a complex report or query, it just seems like Reporting Services struggles to load all the objects the first time and I am at a loss as to how to correct it permanently so that the performance of this report is acceptable under the parameters
I described where it is run sparingly at times.
I know this is a common problem with SSRS through the years, but the performance of the SQL 2016 SSRS seems to be worse than ever. I have patched the SSRS installation with the latest version of SQL 2016.
What else can I do to get this to perform with a reasonable amount of responsiveness?
DWM