Assume that you have a table that has the sql_variant data type in Microsoft SQL Server 2012 or in Microsoft SQL Server 2014. When the statistics are updated manually or automatically, you receive the following error message:

Location: <File Path>\_retypesbase.inl:526
Expression: PbValGetConst()[CSsVariant::OFF_VER] == CSsVariant::CURR_VER
SPID: xx
Process ID: xxxxxx
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.

NoteDBCC CHECKDB ('<database name>') WITH NO_INFOMSGS does not report any database inconsistencies.

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!