Symptoms

Assume that you have the target recovery time of a database set to a nonzero value in Microsoft SQL Server 2012,2014 or 2016. If an assertion occurs during the checkpoint process, the assertion causes a lease timeout on the database, and you receive the following dump file:

date time  spid14s Error: 17066, Severity: 16, State: 1.
date time spid14s SQL Server Assertion: File: <recoveryunit.cpp>, line=7849 Failed Assertion = 'm_ReducedDataSlice <= MaxReducedDataSlice'. 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.
date time spid14s Error: 3624, Severity: 20, State: 1.
date time spid14s 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.
date time spid14s Error: 18400, Severity: 16, State: 1.
date time spid14s The background checkpoint thread has encountered an unrecoverable error. The checkpoint process is terminating so that the thread can clean up its resources. This is an informational message only. No user action is required.

Resolution

This issue is fixed in the following cumulative updates for SQL Server:

Cumulative Update 7 for SQL Server 2012 Service Pack 3

Cumulative Update 3 for SQL Server 2014 Service Pack 2 

Cumulative Update 10 for SQL Server 2014 Service Pack 1

Cumulative Update 4 for SQL Server 2016

Cumulative Update 1 for SQL Server 2016 SP1


About cumulative updates for SQL Server

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:

    Latest cumulative update for SQL Server 2012 SP3

Latest cumulative update for SQL Server 2014    Latest cumulative update for SQL Server 2016


Workaround

To work around this issue, set the target recovery time to zero for the affected database.

Status

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

References

Learn about the terminology Microsoft uses to describe software updates.

Need more help?

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

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×