Performance related issues are often caused by poor report design or an incorrectly configured report server. Below are a few of the common reasons for poor performance when using reports.
The best way to improve report performance is by limiting the data that is used in each report and sub-report. This is accomplished by adding parameters that users must specify when they run the report, such as date ranges or owner, or by adding additional selection criteria to a report. This will greatly reduce the data that is filtered for the report each time it is run by a user.
NOTE: For more information on writing reports using SQL Reporting Services refer to training variety of published resources available from Microsoft.
If there is a noticeable delay (5 seconds or more) in displaying data in a Microsoft Dynamics CRM list, or when opening a Microsoft Dynamics CRM form on a local area network, it could be caused by configuration problems in the SQL Reporting Server (SRS). Typically, this only occurs when Microsoft Dynamics CRM is installed on a separate server from the SRS server.
Reasons for this delay can include the following:
*Incorrect SRS locations in the SQLRSServerURL registry key in HKEY_LOCAL_MACHINE_SOFTWARE Microsoft MSCRM
*Missing or invalid Service Principal Names (SPNs) for the Host name or Microsoft SQL Server (both the SQL Server that contains the Microsoft Dynamics CRM databases and the SRS Microsoft SQL Server)
*Incorrect permissions on the computer that is running Microsoft SQL Server for SRS
NOTE: Incorrect permissions can cause problems accessing Microsoft Dynamics CRM reports. This can prevent Microsoft Dynamics CRM from displaying the list of valid reports in lists and forms.