FIX: The dtasp_PruneTrackingdatabase() stored procedure may take many hours to clean up the DTA database in BizTalk Server 2004

In Microsoft BizTalk Server 2004, the BizTalk Server Software Development Kit (SDK) Samples\Admin\Database Maintenance folder contains the Purge_DTADB.sql script. You can run this script to create the dtasp_PruneTrackingdatabase() stored procedure. Then, you can use this stored procedure to clear information from the BizTalk Server Document Tracking and Activity (DTA) database.

However, when you run the dtasp_PruneTrackingdatabase() stored procedure to clean up your DTA database, you may experience the following symptom. If your DTA database is large, the dtasp_PruneTrackingdatabase() procedure may take many hours to finish the cleanup operation. For example, the dtasp_PruneTrackingdatabase() procedure might require 20 hours or more to clean up a DTA database that is larger than 10 gigabytes (GB).

This problem occurs because of the method that the dtasp_PruneTrackingdatabase() procedure uses to clear information from the DTA database.

To clear information from the database, the dtasp_PruneTrackingdatabase() procedure removes the particular row from the database table instead of removing and then re-creating the whole table. Therefore, it might take a long time for the dtasp_PruneTrackingdatabase() procedure to finish purging the DTA database.

Note While there is some default information that must be written to some tables in the DTA database, it is generally quicker for a procedure to remove and then re-create the whole table than to remove rows from the particular database table.

Hotfix information

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 this specific problem. 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

No prerequisites are required to install this hotfix.

Restart requirement

You do not have to restart your computer 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 item in Control Panel.Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Hotfix installation information

This hotfix contains a Microsoft SQL Server 2000 script that is optimized for cleaning up the existing BizTalk Server DTA database of all completed instance information. After you run this script, only information about instances that have not yet finished running remains in the DTA database. This cleanup process runs quickly when the number of incomplete instances in the tracking database is low. To run this script, follow these steps:

1. Shut down all the BizTalk Server-related services that are on the computer.
2. Back up your BizTalk Server DTA database to make sure that you can recover it if a disaster occurs.
3. Run the hotfix package to extract the Bts_tracking_shrinkexistingdatabase.sql script.
4. Run the Bts_tracking_shrinkexistingdatabase.sql script by using SQL Query Analyzer. To do this, follow these steps:
   1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.
   2. In the SQL Server list, type the name of the computer that is running SQL Server 2000, click the option that you want to use to authenticate with SQL Server 2000, and then click OK.
   3. On the Query menu, click Change Database, click your BizTalk Server DTA database, and then click OK. For example, click BizTalkDTADb, and then click OK.
   4. On the File menu, click Open, locate and then click the Bts_tracking_shrinkexistingdatabase.sql file that you extracted, and then click Open.
   5. Press F5 to run the script.

When this script runs, it creates several tables together with a stored procedure. Then, the cleanup process runs. This script is a simple script and it typically runs very quickly. However, you may want to test this script against a large database to determine whether it runs quickly enough for your requirements.

Important When you use the dtasp_PruneTrackingdatabase() stored procedure to clean up the BizTalk Server DTA database, you can configure the dtasp_PruneTrackingdatabase() stored procedure to clear items that are earlier than a particular date. You cannot configure the Bts_tracking_shrinkexistingdatabase.sql script to perform this same functionality. The Bts_tracking_shrinkexistingdatabase.sql script truncates the tables in the DTA to clear all completed instances from the DTA database. Incomplete instances are not removed.

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

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