FIX: A database is marked as suspect when you update a table that contains a nonclustered index in SQL Server 2005

Article translations Article translations
Article ID: 934734 - View products that this article applies to.
Bug: #50001024 (SQL Hotfix)
Notice
Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.
Expand all | Collapse all

On This Page

SUMMARY

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

SYMPTOMS

When you update a table that contains a nonclustered index in a Microsoft SQL Server 2005 database, the database is marked as suspect. Additionally, an error message that resembles the following is logged in the SQL Server 2005 Errorlog file:
Date Time SPID SQL Server Assertion: File: <page.cpp>, line=3436 Failed Assertion = 'IsValidSlot (sid)'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Date Time SPID Error: 3624, Severity: 20, State: 1.
Date Time SPID A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Date Time SPID Error: 3314, Severity: 21, State: 1.
Date Time SPID During undoing of a logged operation in database 'odstjm', an error occurred at log record ID (82:641734:321). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
This problem occurs if the allow_page_locks option is disabled for the table that does not have a clustered index.

RESOLUTION

Cumulative update information

To resolve this problem, obtain cumulative update package 2 for SQL Server 2005 Service Pack 2 (build 3175). For more information about how to obtain cumulative update package 2 (build 3175), click the following article number to view the article in the Microsoft Knowledge Base:
936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available

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:
http://support.microsoft.com/contactus/?ws=support
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 SQL Server 2005 Service Pack 2 installed to install this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

Restart information

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

Registry information

You do not have to change the registry.

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 of 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 item in Control Panel.
SQL Server 2005 32-bit version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3166.0296,30428-Apr-200702:53x86
Msmdlocal.dll9.0.3166.015,943,53628-Apr-200702:53x86
Mssqlsystemresource.ldfNot Applicable524,28827-Apr-200719:05Not Applicable
Mssqlsystemresource.mdfNot Applicable40,173,56827-Apr-200719:05Not Applicable
Rdistcom.dll2005.90.3166.0644,46428-Apr-200702:53x86
Sqlaccess.dll2005.90.3166.0350,57628-Apr-200702:53x86
Sqlservr.exe2005.90.3166.029,190,51228-Apr-200702:53x86
Sysdbupg.sqlNot Applicable510,62226-Apr-200710:04Not Applicable
SQL Server 2005 x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3166.0296,30428-Apr-200702:53x86
Msmdlocal.dll9.0.3166.015,943,53628-Apr-200702:53x86
Mssqlsystemresource.ldfNot Applicable524,28827-Apr-200719:05Not Applicable
Mssqlsystemresource.mdfNot Applicable40,173,56827-Apr-200719:05Not Applicable
Rdistcom.dll2005.90.3166.0828,27228-Apr-200716:12x64
Sqlaccess.dll2005.90.3166.0357,74428-Apr-200716:12x86
Sqlservr.exe2005.90.3166.038,509,93628-Apr-200716:12x64
Sysdbupg.sqlNot Applicable510,62226-Apr-200710:04Not Applicable
SQL Server 2005 Itanium architecture version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3166.0296,30428-Apr-200702:53x86
Msmdlocal.dll9.0.3166.049,887,08828-Apr-200710:09IA-64
Mssqlsystemresource.ldfNot Applicable524,28827-Apr-200719:05Not Applicable
Mssqlsystemresource.mdfNot Applicable40,173,56827-Apr-200719:05Not Applicable
Rdistcom.dll2005.90.3166.01,885,04028-Apr-200710:09IA-64
Sqlaccess.dll2005.90.3166.0352,11228-Apr-200710:09x86
Sqlservr.exe2005.90.3166.072,626,03228-Apr-200710:09IA-64
Sysdbupg.sqlNot Applicable510,62226-Apr-200710:04Not Applicable

WORKAROUND

To work around this issue, enable the allow_page_locks option for the nonclustered index.

STATUS

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

MORE INFORMATION

You can run the following statement against a database to find out whether any tables in the database may have this problem:
select * from sys.indexes where index_id = 0 and allow_page_locks = 0 
For more information about the naming schema for 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

Properties

Article ID: 934734 - Last Review: October 8, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbautohotfix kbsql2005engine kbexpertiseadvanced kbfix kbqfe kbHotfixServer KB934734

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com