October 16, 2008 at 12:34 am
On SQL2005 i ran a DB Update script. Among a lot of other things it does (re)create a lot of indexes. On a few indexes we get the following error:
ERROR : 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.
Now i tried DBCC with all different options, but it did not find any corruption.
In an effort to resolve this issue i also applied the latest hotfix, SQLServer2005-KB953752-x86-ENU.exe. This did not fix the problem.
Is this a bug, will we need to have Microsoft have a look at it?
June 28, 2010 at 1:14 am
I encountered the same error as well. Does anyone has any solution for this? Kindly advice.
Regards,monkeyDBAWe dont grow when things are easy; We grow when we face challenges.
October 14, 2011 at 9:32 am
Me too.
Getting this error running an INSERT statement with (TABLOCK). Resulting in a Stack dump. The table is NOT compressed/replicated, CHECKDB does not reveal any errors. Using SQL Server 2008 R2 build 10.50.1600.1 (no Service Packs).
Error log excerpts :
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.
SQL Server Assertion: File: <pageref.cpp>, line=922 Failed Assertion = 'IS_OFF (BUF_MINLOGGED, m_buf->bstat) || pageModifyType != PageModifyType_Contents || GetPagePtr ()->IsTextPage ()'. 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.
October 14, 2011 at 10:42 am
Call Microsoft Customer Support.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy