- An assertion failure occurs, and the following error is logged in the SQL Server error log:
Date Timespid# Error: 17066, Severity: 16, State: 1.
Date Timespid# SQL Server Assertion: File: pageref.cpp, line=1332 Failed Assertion = '0 == pageFull'. 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 Timespid# 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.
- The query returns incorrect results.
- A data corruption issue occurs.