Select the product you need help with
FIX: "A system assertion check has failed" error when you re-create a nonclustered index on a column in SQL Server 2008 R2 or in SQL Server 2012Article ID: 2728534 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 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 2008 R2 Service Pack 1 fix release. On This PageSymptomsConsider the following scenario:
Location: sobuild.c:3392 Expression: CompareRow ( rightPageRow, *m_pSEBindings, keyCnt, *pHobtAccess, PAGE_LEAF_LEVEL) SPID: 53 Process ID: 3268 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. Note This issue occurs when you run a query that uses parallelism in the query execution plan. CauseThis issue occurs because the Collation ID in storage engine metadata is not synchronized with the Collation ID in metadata. ResolutionCumulative update informationCumulative update package 1 for SQL Server 2012 Service Pack 1The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:2765331 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 2012 fix release. We recommend 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:
(http://support.microsoft.com/kb/2765331/
)
Cumulative update package 1 for SQL Server 2012 Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was releasedSQL Server 2008 R2 Service Pack 2The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:2754552 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 2008 R2 Service Pack 2 fix release. We recommend 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:
(http://support.microsoft.com/kb/2754552/
)
Cumulative update package 3 for SQL Server 2008 R2 Service Pack 2
2730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released
SQL Server 2012The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:2758687 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 2012 fix release. We recommend 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:
(http://support.microsoft.com/kb/2758687/
)
Cumulative update package 4 for SQL Server 2012
2692828
(http://support.microsoft.com/kb/2692828/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released
SQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:2723743 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 2008 R2 Service Pack 1 fix release. We recommend 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:
(http://support.microsoft.com/kb/2723743/
)
Cumulative update package 8 for SQL Server 2008 R2 Service Pack 12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was releasedWorkaroundTo work around this issue, add the MAXDOP=1 query hint option to the query that you use to re-create the nonclustered index. StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2728534 - Last Review: November 20, 2012 - Revision: 4.0 Applies to
|  |
Back to the top
