İsmail Ozcan

Microsoft SQL Server Reporting Services periodically restarts, and each restart clears the Reporting Services cache. After this cache has been cleared, it may take some time for the next report that is run to display. For example, you may have noticed that it takes a really long time for the first report that is run each morning to display. To minimize the effect of Reporting Services restarts, a new class that is named  SRSReportServerWarmup  is included with cumulative update 7 for Microsoft Dynamics AX 2012 R2. When the SRSReportServerWarmup class runs, it prepares the report server for use by performing the following tasks: Loads Microsoft Dynamics AX business logic assemblies. Connects to Reporting Services. Runs a sample report that is named SRSReportServerWarmup. As a best practice, you should schedule the batch job that runs the SRSReportServerWarmup class to run immediately after Reporting Services restarts. For more information about how to configure the ba...

Czesława Langowska Vliegen   18 Sep 2013 3:12 AM  0 There are some tips we can use to improve performance of reports for Dynamics AX 2012. Use static reports. The deployment of static reports is described here:  http://technet.microsoft.com/en-us/library/hh496446.aspx  In this way we will safe several calls to Metadata service to get labels values and correct formatting of dates and numbers. Install application hotfix KB 2879661 which fix the situation when first generation of a report after Dynamics AX client restart takes long. This happens for each user. Newest kernel . Hotfixes for performance improvement are included in new kernels that are released; sometimes there is a dramatic impact on performance. In the morning a first report generation takes a lot of time SSRS uses session pooling. The first request that comes in from a user – a session will be created for them within the AOS services. Each user gets a session cached on the AOS service...