Applies ToSQL Server 2012 Enterprise SQL Server 2012 Standard SQL Server 2012 Developer SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use)

Symptoms

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:526Expression: PbValGetConst()[CSsVariant::OFF_VER] == CSsVariant::CURR_VERSPID: xxProcess ID: xxxxxxMsg 3624, Level 20, State 1, Line 1A 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:

Status

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

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.