FIX: You may experience concurrency issues when you run the DBCC INDEXDEFRAG statement in SQL Server 2000 (907250)


The information in this article applies to:

  • Microsoft SQL Server 2000 Desktop Engine (MSDE)
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Workgroup Edition
  • Microsoft SQL Server 2000 Developer Edition 64 bit
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
Bug #: 474645 (SQL Server 8.0)
Microsoft distributes SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you apply this hotfix package
  • Whether this hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply this hotfix package
  • The files that are contained in this hotfix package

SYMPTOMS

When you run the DBCC INDEXDEFRAG statement, null mode page locks may accumulate on defragmented pages. These page locks may consume server resources. Then, the transactions that accumulate the locks try to escalate the page locks to table locks. The transactions escalate the page locks to try to reduce server resource usage. Because the DBCC INDEXDEFRAG statement takes an exclusive page lock and also causes the lock escalation to occur, you may experience concurrency issues.

Note You can use the sp_lock stored procedure to verify the mode of a lock.

For a list of all publicly released Microsoft SQL Server 2000 Post-Service Pack 4 hotfixes, see the following article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 SP4

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 Microsoft SQL Server 2000 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:

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.

Prerequisites

Microsoft SQL Server 2000 Service Pack 4 (SP4)

For information about how to obtain SQL Server 2000 SP4, see the following article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

Restart information

You must restart the computer after you apply this hotfix.

Registry information

You do not have to make changes to the registry after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

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.SQL Server 2000, 32-bit versions
File nameFile versionFile sizeDateTimePlatform
Updatelauncher.exe5.2.3790.12888,70415-Sep-200518:30x86
Spupdsvc.exe6.1.22.525,82401-Jun-200518:22x64
Tempcatsign.cdfNot Applicable1,30215-Sep-200523:42Not Applicable
Mssdi98.dll8.11.50523.0239,10406-Jun-200523:46x86
Ntwdblib.dll2000.80.2159.0290,81615-Sep-200521:37x86
Odsole70.dll2000.80.2159.069,63215-Sep-200521:37x86
Osql.exe2000.80.2039.057,34404-May-200505:32x86
Pfclnt80.dll2000.80.2159.0430,08015-Sep-200521:37x86
Procsyst.sqlNot Applicable552,06817-Jun-200501:15Not Applicable
Replprov.dll2000.80.2159.0237,56815-Sep-200521:37x86
Semexec.dll2000.80.2159.0856,06415-Sep-200521:37x86
Sp4_serv_qfe.sqlNot Applicable18,81017-Jun-200501:15Not Applicable
Sqlagent.exe2000.80.2159.0323,58415-Sep-200520:04x86
Sqldiag.exe2000.80.2159.0118,78415-Sep-200520:52x86
Sqldmo.dll2000.80.2159.04,362,24015-Sep-200521:37x86
Sqlevn70.rll2000.80.2159.045,05615-Sep-200521:37Not Applicable
Sqlfth75.dll2000.80.2159.0102,40015-Sep-200520:12x86
Sqlservr.exe2000.80.2159.09,158,65615-Sep-200521:40x86
Stardds.dll2000.80.2159.0176,12815-Sep-200521:37x86
Svrnetcn.dll2000.80.2159.0110,59215-Sep-200521:37x86
Ums.dll2000.80.2159.035,32815-Sep-200521:37x86
Osql.exe2000.80.2039.057,34404-May-200505:32x86
Sqlstpcustomdll.dll1.0.128.01,367,04002-Aug-200500:12x64
Sqlstpcustomdll.rllNot Applicable25,08802-Aug-200500:12Not Applicable
Spupdsvc.exe6.1.22.522,75201-Jun-200518:22x86
Tempcatsign.cdfNot Applicable1,30215-Sep-200523:39Not Applicable
Mssdi98.dll8.11.50523.0239,10406-Jun-200523:46x86
Ntwdblib.dll2000.80.2159.0290,81615-Sep-200521:37x86
Odsole70.dll2000.80.2159.069,63215-Sep-200521:37x86
Osql.exe2000.80.2039.057,34404-May-200505:32x86
Pfclnt80.dll2000.80.2159.0430,08015-Sep-200521:37x86
Procsyst.sqlNot Applicable552,06817-Jun-200501:15Not Applicable
Replprov.dll2000.80.2159.0237,56815-Sep-200521:37x86
Semexec.dll2000.80.2159.0856,06415-Sep-200521:37x86
Sp4_serv_qfe.sqlNot Applicable18,81017-Jun-200501:15Not Applicable
Sqlagent.exe2000.80.2159.0323,58415-Sep-200520:04x86
Sqldiag.exe2000.80.2159.0118,78415-Sep-200520:52x86
Sqldmo.dll2000.80.2159.04,362,24015-Sep-200521:37x86
Sqlevn70.rll2000.80.2159.045,05615-Sep-200521:37Not Applicable
Sqlfth75.dll2000.80.2159.0102,40015-Sep-200520:12x86
Sqlservr.exe2000.80.2159.09,158,65615-Sep-200521:40x86
Stardds.dll2000.80.2159.0176,12815-Sep-200521:37x86
Svrnetcn.dll2000.80.2159.0110,59215-Sep-200521:37x86
Ums.dll2000.80.2159.035,32815-Sep-200521:37x86
Osql.exe2000.80.2039.057,34404-May-200505:32x86
Sqlstpcustomdll.dll1.0.128.0943,10401-Aug-200523:55x86
Sqlstpcustomdll.rllNot Applicable24,57601-Aug-200523:55Not Applicable
SQL Server 2000, 64-bit version
File nameFile versionFile sizeDateTimePlatform
Osql.exe2000.80.2039.0149,50415-Sep-200519:53IA-64
Sp4_serv_qfe.sqlNot Applicable18,81017-Jun-200501:15Not Applicable
Sqlrun.mspNot Applicable17,408,00016-Sep-200513:48Not Applicable
Note Because of file dependencies, the most recent hotfix or feature that contains these files may contain additional files.

WORKAROUND

To work around this problem, turn on trace flag 1211 on the connection that runs the DBCC INDEXDEFRAG stored procedure. Trace flag 1211 prevents the transactions that accumulate the locks from escalating the page locks to table locks. The null mode locks may still accumulate. If the null mode locks accumulate, you may receive an error message that is similar to the following:
Error : 1204, Severity: 19, State: 3 SQL Server has run out of LOCKS. Re-run your command when there are fewer active users, or ask your System Administrator to reconfigure SQL Server with more LOCKS
Note We only recommend this workaround as a short-term solution. You should only turn on trace flag 1211 for the duration of the DBCC INDEXDEFRAG stored procedure. If you leave the trace flag on continuously, or if you use this trace flag as a startup parameter, you may experience additional issues from the side effects that are associated with this trace flag. We recommend that you only enable this trace flag for the duration of the DBCC INDEXDEFRAG stored procedure to avoid these issues.

STATUS

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

MORE INFORMATION

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, 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

Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbfix kbbug kbHotfixServer kbQFE kbpubtypekc KB907250 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.