FIX: The Dta_purge_old_records Stored Procedure May Cause Exclusive Table Locking (327467)


The information in this article applies to:

  • Microsoft BizTalk Server 2002
This article was previously published under Q327467

SYMPTOMS

When you execute the Dta_purge_old_records stored procedure to archive or remove your tracking database, you may experience exclusive table locks. These table locks cause table locking problems with other processes that are trying to access the tracking database.

CAUSE

If the execution of the Dta_purge_old_records stored procedure affects many rows, Microsoft SQL Server uses an optimization hint to use exclusive table locks for the process.

RESOLUTION

Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

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

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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 fix has the file attributes (or later) 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      Size    File name
   -----------------------------------------------------------
   06-Aug-2002  21:25     72,992  Bts_tracking_cleanup_job.sql
Note Because of file dependencies, the most recent hotfix or feature 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 at the beginning of this article. This problem was first corrected in Microsoft BizTalk Server 2002 Service Pack 1.

MORE INFORMATION

This version of the stored procedure supersedes all previous versions of the archive and purging stored procedures that are included in earlier versions of BizTalk Server. To install this hotfix, follow these steps:
  1. Save BTS_Tracking_Cleanup_Job.sql to a temporary location on the hard disk of the computer running SQL Server.
  2. Click Start, point to Programs, point to Microsoft SQL Server, and then click Query Analyzer.
  3. Enter the correct connection information, and then click OK.
  4. Change the database context to your tracking database. By default, this tracking database is InterchangeDTA.
  5. Click File, and then click Open.
  6. Locate the file that you saved in step 1, and then click Open.

    Note If your tracking database has a name other than InterchangeDTA, find all instances of InterchangeDTA in this text window and replace InterchangeDTA with the name of your tracking database.
  7. Click Query, and then click Execute.
Modification Type:MinorLast Reviewed:10/17/2005
Keywords:kbHotfixServer kbQFE kbBizTalk2002SP1fix kbbug kbfix KB327467 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.