{"id":14378,"date":"2018-01-04T11:14:36","date_gmt":"2018-01-04T11:14:36","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=14378"},"modified":"2023-09-06T11:35:19","modified_gmt":"2023-09-06T11:35:19","slug":"sql-database-error-3624-a-system-assertion-check-has-failed","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/sql-database-error-3624-a-system-assertion-check-has-failed\/","title":{"rendered":"SQL Database Error 3624 – a system assertion check has failed"},"content":{"rendered":"

At times, when SQL Administrator tries to move the database from one SQL server to another, they may encounter the following error message:<\/p>

Location: statutil.cpp:4128
Expression: iKey < m_statBlob.GetHeader()->GetKeyCount()
SPID: 59 Process ID: 1732
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.<\/em><\/p>

Reasons for Error 3624<\/strong><\/h2>
    \n
  1. The Query derives data by means of the JOIN statement for two or more tables<\/li>\n\n\n\n
  2. Data compression enabled for only one table<\/li>\n\n\n\n
  3. Clustered Index key available on a column of the table<\/li>\n\n\n\n
  4. The column length in one table differs from column length on other tables<\/li>\n\n\n\n
  5. ON-filter enabled for the column<\/li>\n\n\n\n
  6. Either the SQL server performs an operation with LOOP JOIN join-hint or this hint is used by Query<\/li>\n<\/ol>

    The result is that the length of key data is bigger than the length of the compressed key value buffer, thus causing the “SQL Database Error 3624 – a system assertion check has failed”. However, the assertion failure may also be caused due to a software bug or corruption in the database.<\/p>

    Try to find the cause of the error by running the DBCC CHECKDB command and work to resolve the error with most suitable SQL Database recovery option.<\/p>

    How to Resolve SQL Database Error 3624<\/strong><\/h2>
      \n
    1. Check Database consistency: <\/strong>DBCC CHECKDB command lets you analyze the exact cause of the error, for example, whether the error is caused due to database corruption or due to a bug in the software’s previous release. Database corruption can be repaired but up to a certain level only.<\/li>\n\n\n\n
    2. Restore Database from Backup: In case the corruption is too high, try to restore the database from backup<\/a>, however, check the status before restoring the database from backup. Backup should be up-to-date for restoration and not available in any of the following forms:\n