FIX: BizTalk Server 2004 performance may be poor and your CPU utilization may be high on the SQL Server-based server that hosts the BizTalk Server databases (892491)



The information in this article applies to:

  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Service Pack 1
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Developer Edition

SYMPTOMS

You may notice that Microsoft BizTalk Server performance is very poor and that the CPU utilization is 80 percent or more on the SQL Server-based server that hosts the BizTalk Server databases. You may also notice that the stored procedure bts_FindSubscriptions consumes many CPU cycles on the SQL Server-based server.

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 BizTalk Server 2004 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.

Prerequisites

You must have BizTalk Server 2004 Service Pack 1 (SP1) installed before you install this hotfix.

Restart requirement

You must restart the BizTalk Server Application Service after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 tool in Control Panel.
   Date         Time   Version     Size     File name
   ----------------------------------------------------------------------------
   11-Jan-2005  23:53  3.0.5372.0  221,184  Microsoft.xlangs.biztalk.engine.dll  
   11-Jan-2005  23:53  3.0.5372.0  217,088  Microsoft.xlangs.engine.dll  
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Under certain circumstances, a non-optimal query is generated to be used by the bts_FindSubscriptions stored procedure. In this scenario, the bts_FindSubscriptions stored procedure becomes very inefficient and consumes a larger than expected percentage of CPU cycles on the SQL Server-based server. In this scenario, the bts_FindSubscriptions stored procedure becomes a bottleneck for processing documents in BizTalk Server.

This problem occurs if any one of the values that are returned to the count field for the following query are more than 20:
Use BizTalkMsgBoxDb
SELECT TOP 5 COUNT(*) as count, uidPropID, vtValue FROM EqualsPredicates GROUP BY uidPropID, vtValue HAVING COUNT(*) > 5 ORDER BY count DESC
Note BizTalkMsgBoxDb is a placeholder for the actual name of the BizTalk Server MessageBox database on your SQL Server-based server. If the name of your BizTalk MessageBox database is not BizTalkMsgBoxDb, you must substitute the correct name of your BizTalk MessageBox database before you run this query.

Modification Type:MinorLast Reviewed:9/8/2006
Keywords:kbbiztalk2004-2006swept kbQFE kbBizTalk2004preSP1fix kbbug kbfix kbHotfixServer KB892491 kbAudDeveloper