monitor
#monitor#3624

3624

Product

Name

Event ID

3624

Event

Source

MSSQLSERVER

Component

SQLEngine

Symbolic

Name

SYS_ASSERTFAIL

Message

Text

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 Hotfix from Technical Support.

Asserts are statements placed in the code of an application to ensure that certain conditions

are satisfied. In that respect an assert behaves similar to an error. You can think of asserts as

emphatic, firm errors. The condition specified must be met for the program to continue regular

execution. If the condition isn’t met, the assert is raised. For more information, see

C/C++

Assertions.

uses asserts in many places to ensure that conditions are true. For example, the

condition ‘existingState == DB_Unencrypted’ asserts that a database state is unencrypted

before the next command in the code is run. If that’s not the case, the assert is raised. Error

3624 notifies you that such a condition wasn’t met and an assert was raised.

Error 3624 is raised together with

MSSQLSERVER_17066. Here are examples of how you can

see these errors in the SQL Server error log. You’ll also see the assert condition raised during

Expand table