Your users complain that performance is really bad when the first report is created in the morning?
- Ask the administrators whether the „Warmup SSRS Reports“ batch job is scheduled to run every morning (before the first user typically logs in). You can also check yourself for that batch job, if you have access to System Administration > Inquiries > Batch Jobs > Batch Jobs. Look for an entry similar to the following – it will probably be scheduled to run once a day, early in the morning.
What does this do? This batch job will, so to say, wake up the SSRS server so that this is not done by the first user printing the first report in the morning.
- If the report is not running and you are allowed to put it into batch processing yourself, do the following:
- In the AOT, go to MenuItems > Output > SRSReportServerWarmup and open that entry.
- On the „Batch“ tab page,
- set the check box for batch processing.
- enter a good task description, like „Warmup Report Server“
- set the recurrance to daily, in the morning.
- Additionally, you might discuss with your developers whether it makes sense to include some reports explicitly in the warmup process.
What does this do? The batch job will then not only „warmup“ the server but those reports will have been „prepared“ for execution, too.
Your administrator and developers will find many technical references when searching for “warmup ssrs” and “dynamics AX” in their favorite search engine. To get started, they can look here: https://technet.microsoft.com/en-us/library/dn527683.aspx
- This is not a cure for badly constructed reports!
- The warmup feature is included in CU7. If the application is not there yet, let your developers try to import it from CU7.