FIX: Error message when you try to rebuild one partition of an index on an indexed view in SQL Server 2005: "A system assertion check has failed. Check the SQL Server error log for details."

Article ID: 970726 - View products that this article applies to.
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

SYMPTOMS

Consider the following scenario:
  • In Microsoft SQL Server 2005, you have a table that contains multiple partitions.
  • You create an indexed view on this table.
  • You try to rebuild one partition of an index on the indexed view. For example, you run a command that resembles the following:
    ALTER INDEX <index name> on <indexed view> REBUILD PARTITION=<Partition Number>
In this scenario, you may receive the following assertion:
Location: "xisort.cpp":305
Expression: !(0 == pvrPartition) || (1 == m_cFgidSort)
SPID: 60
Process ID: 2308
Msg 3624, Level 20, State 1, Line 1
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.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

When this problem occurs, a mini-dump file is generated in the SQL Server log folder. Additionally, the following error message is logged in the SQL Server error log file:
<Date><Time> spid65 Error: 17066, Severity: 16, State: 1.
<Date><Time> spid65 SQL Server Assertion: File: <"xisort.cpp">, line=305 Failed Assertion = '!(0 == pvrPartition) || (1 == m_cFgidSort)'. 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> spid65 Error: 3624, Severity: 20, State: 1.
<Date><Time> spid65 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> spid53 Using 'dbghelp.dll' version '4.0.5'
<Date><Time> spid53 **Dump thread - spid = 53, PSS = 0x00000001AC205BF0, EC = 0x00000001AC205C00
<Date><Time> spid53 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0009.txt
<Date><Time> spid53 *
*******************************************************************************
<Date><Time> spid53 *
<Date><Time> spid53 * BEGIN STACK DUMP:
<Date><Time> spid53 * 04/18/09 10:41:16 spid 53
<Date><Time> spid53 *
<Date><Time> spid53 * Location: "xisort.cpp":305
<Date><Time> spid53 * Expression: !(0 == pvrPartition) || (1 == m_cFgidSort)
<Date><Time> spid53 * SPID: 53
<Date><Time> spid53 * Process ID: 1488
<Date><Time> spid53 *
<Date><Time> spid53 * Input Buffer 228 bytes -
<Date><Time> spid53 * <Alter Index statement>
Back to the top | Give Feedback

CAUSE

When the server is rebuilding the index, the optimizer generates a plan which is inconsistent internally. The inconsistent plan is generated when the optimizer decides to recompute the view. This behavior causes the problem that is mentioned in the "Symptoms" section.
Back to the top | Give Feedback

RESOLUTION

The fix for this issue was first released in Cumulative Update 5 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
972511
(http://support.microsoft.com/kb/972511 /LN/ )
Cumulative update package 5 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598
(http://support.microsoft.com/kb/960598/LN/ )
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Back to the top | Give Feedback

WORKAROUND

To work around this problem, perform the reindex operation on all partitions.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

REFERENCES

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/ )
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
913089
(http://support.microsoft.com/kb/913089/ )
How to obtain the latest service pack for SQL Server 2005
For more information about the new features in SQL Server 2005 Service Pack 3 (SP3) and about the improvements in SQL Server 2005 SP3, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=131442
(http://go.microsoft.com/fwlink/?LinkId=131442)
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
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 970726 - Last Review: August 17, 2009 - Revision: 1.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbsurveynew kbexpertiseadvanced kbqfe kbfix KB970726
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top