İ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...

AX utilizes SQL Indexes in order to speed up queries to the database. It is important that any index created is analyzed for its usage pattern; for example, will the query only be made once per day, or thousands of times in a loop? It might not be worth it to create an index for a query which is only executed once per day. The reason for this is that anytime an INSERT, UPDATE or DELETE statement is executed, any affected indexes must also be updated. A side effect from a lot of INSERT, UDPATE or DELETE statements is that over time that index can become fragmented. Fragmentation occurs when SQL can no longer fit data into the free space allocated for an index, or space is removed within the middle of a page of data. It handles this by creating another page for the index to store its data in. Excessive fragmentation can lead to poor performance if a lot of records are being selected as the data is not kept contiguous. This can lead to increased IO and CPU. One workload that is particu...