FIX: SQL connections to BizTalk databases are not cleaned up or reused when you use the BiztalkOperations class in BizTalk Server 2006 R2 or BizTalk Server 2009

View products that this article applies to.

Symptoms

Consider the following scenario:

You have a computer that is running Microsoft BizTalk Server 2006 R2 or BizTalk Server 2009.
You develop a program to access information that is displayed on the Group Hub page in the BizTalk Administration Management Console by using the BizTalkOperations class.

In this scenario, you run the program, and many SQL connections to the various BizTalk databases are opened. However, these SQL connections are not cleaned up or reused. They are only removed when you exit the program. Therefore, after the program is running for some time, the memory usage by SQL Server increases. When this problem occurs, the program experiences poor performance.

Note You can monitor SQL connections in SQL Server Management Studio by using the Activity Monitor.

For example, you write the following code to extract the IBaseMessage.BodyPart property of messages from the BizTalk MessageBox database (BizTalkMsgBoxDb) by using the BizTalkOperations.GetMessages() method:

BizTalkOperations operation = new BizTalkOperations();
IEnumerable bizTalkMsgs = operation.GetMessages();
foreach (BizTalkMessage msg in bizTalkMsgs)
{
string hostname=msg.HostName; 
IBaseMessagePart bodyPart = msg.BodyPart; 
...
}

When you run the program, a SQL connection is created every time that a bodyPart property is accessed.

↑ Back to the top

Cause

This problem occurs because there is an error in the connection string that theBizTalkOperations class uses to connect to the BizTalk MessageBox database.

↑ Back to the top

Resolution

After you apply this hotfix, connection pooling is enabled when you use the BizTalkOperations class to access the BizTalk databases. SQL connections can be reused and the performance is improved.

Cumulative updated information

For BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2429050 Cumulative update package 1 for BizTalk Server 2009

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 BizTalk Server 2006 R2 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

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 version	File size	Date	Time	Platform
Microsoft.biztalk.dbaccessor.dll	3.6.1549.2	18,288	20-Oct-2009	16:12	x86

Prerequisites

You must have BizTalk Server 2006 R2 installed to apply this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

↑ Back to the top

Status

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

↑ Back to the top

More information

For more information about the BizTalkOperations class and the BizTalkOperations.GetMessage method, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/en-us/library/microsoft.biztalk.operations.biztalkoperations.getmessage%28BTS.10%29.aspx

For more information about the IBaseMessage.BodyPart property, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/en-us/library/microsoft.biztalk.message.interop.ibasemessage.bodypart%28BTS.10%29.aspx

For more information about SQL Server Connection Pooling, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/en-us/library/8xx3tyca.aspx

For more information about how to install BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information on BizTalk Server hot fixes

↑ Back to the top