FIX: Data in the TDDS_FailedTrackingData table is not deleted by the DTA Purge and Archive SQL Server Agent job in BizTalk Server

In Microsoft BizTalk Server 2006 R2, you run the DTA Purge and Archive SQL Server Agent job to purge old data from the BizTalk Tracking database (BizTalkDTADb). However, you find that old data in the TDDS_FailedTrackingData table is not deleted by the DTA Purge and Archive job. Therefore, the BizTalkDTADb database grows very large if many tracking failures occur, and then BizTalk Server 2006 R2 may perform more slowly than expected.
Note If you use BizTalk Server 2009, the Event Source and Event Category in above events are �BizTalk Server 2009�.

This problem occurs because the DTA Purge and Archive SQL Server Agent job does not contain an SQL statement to delete rows in the TDDS_FailedTrackingData table.

Hotfix information

Cumulative update information

BizTalk Server 2009

The hotfix that resolves this issue is included in cumulative update package 2 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:�

2497794�Cumulative update package 2 for BizTalk Server 2009

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

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

Restart requirement

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

Hotfix replacement information

This hotfix does not replace 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 item in Control Panel.

For BizTalk Server 2006 R2 SP1

The hotfix that resolves this problem is included in cumulative update package 1 for BizTalk Server 2006 R2 SP1.

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:
For more information about BizTalk Server 2006 R2 SP1 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

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

For more information about how to archive and purge the BizTalk tracking database, visit the following Microsoft Web sites: For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base: