17066

Product

Name

Event ID

17066

Event

Source

MSSQLSERVER

Component

SQLEngine

Symbolic

Name

SQLASSERT_ONLY

Message

Text

Assertion: File: <%s>, line=%d Failed Assertion = ‘%s’. 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.

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_3624. 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 run

ﾉ

Expand table