Article ID: 915722
Article Last Modified on 5/10/2007
APPLIES TO
- Microsoft Dynamics CRM 3.0
The hotfix that is discussed in this article is not available for the Chinese version of Microsoft Dynamics CRM or for the Japanese version of Microsoft Dynamics CRM.
SYMPTOMS
In Microsoft Dynamics CRM 3.0, you experience slower performance than typical when the MSCRM Stored Procedure Priming job is running. You notice one or more of the following symptoms:
- Database records are slower than typical.
- CPU usage is more than typical.
- There are unexpected increases in the following performance counters:
- SQL Server: SQL Statistics: Batch Requests/sec
- SQL Server: SQL Statistics: SQL Compilations/sec
- SQL Server: SQL Statistics: SQL Recompilations/sec
- Physical Disk: Avg Disk Queue Length
CAUSE
This problem occurs because the MSCRM Stored Procedure Priming job exists to keep the Microsoft Dynamics CRM cascading stored procedures in the Microsoft SQL Server procedure cache. By default, the MSCRM Stored Procedure Priming job is scheduled to run every 10 minutes. The frequency of running the job can cause the CPU usage to spike on the SQL Server that contains the Microsoft Dynamics CRM databases.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics CRM 3.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
| File name | File size | Date | Time |
|---|---|---|---|
| Invoice status detail.rdl | 63,436 | 12-Sep-2006 | 23:19 |
| Invoice status.rdl | 31,788 | 12-Sep-2006 | 23:19 |
| Sales pipeline.rdl | 108,507 | 12-Sep-2006 | 23:19 |
| Service activity volume detail.rdl | 100,124 | 12-Sep-2006 | 23:19 |
| Service activity volume.rdl | 65,200 | 12-Sep-2006 | 23:19 |
Installation information
Install this hotfix on computers that are running Microsoft Dynamics CRM 3.0 server.
Prerequisites
There are no prerequisites to apply this hotfix.
Restart requirement
If you are prompted, restart the computer after you install the hotfix.
Removal information
To remove this hotfix from a computer that is running Microsoft Dynamics CRM 3.0 server, use Add or Remove Programs in Control Panel. System administrators can use the Spunist.exe utility to remove this hotfix from a computer that is running Microsoft Dynamics CRM 3.0 server.
The Spuninst.exe tool is located in the %Windir%\$NTUninstallKB915722$\Spuninst folder.
More information about the hotfix
This hotfix resolves this problem only when you are in online mode in the Microsoft Dynamics CRM client for Outlook. This hotfix does not resolve the problem if you are in offline mode in the Microsoft Dynamics CRM laptop client for Outlook.
WORKAROUND
To work around this problem, change the schedule for the MSCRM Stored Procedure Priming job. To do this, follow these steps depending on the version of SQL Server that you are using.
SQL Server 2005
- Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
- Connect to the SQL Server that contains the Microsoft Dynamics CRM databases.
- Click SQL Server Agent.
- Click Jobs, and then double-click MSCRM Stored Procedure Priming Job.
- Click the Schedules tab, and then double-click the Stored Procedure Priming schedule.
- In the Daily frequency box, select the time interval that you want. For example, select 4 hours.
- Click OK to close the dialog boxes.
SQL Server 2000
- Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
- Expand Microsoft SQL Servers, expand SQL Server Group, and then expand the local server.
- Expand Management, and then expand SQL Server Agent.
- Click Jobs, and then double-click MSCRM Stored Procedure Priming Job.
- Click the Schedules tab, and then double-click the listed schedule. The schedule should be set to Recurring.
- Click Change.
- In the Daily frequency box, select the time interval that you want. For example, select 4 hours.
- Click OK to close the dialog boxes.
MORE INFORMATION
For information about performance tuning for CRM 3.0, see the following white paper:
For more information about software update terminology, click the following article numbers to view the articles in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
887283 Microsoft Business Solutions CRM software hotfix and update package naming standards
Additional query words: crm3 crm30 crm3.0 crm 3 hotfix mscrm stored procedure priming
Keywords: kbmbsadministration kbhotfixserver kbqfe kbmbsmigrate kbpubtypekc KB915722
