FIX: Indirect checkpoints on tempdb database cause "Non-yielding scheduler" error in SQL Server 2016 and 2017

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

Symptoms


By default, indirect checkpoints are turned on for the tempdb database in Microsoft SQL Server 2016 and 2017. Under heavy-workload conditions, a "Non-yielding scheduler" error may occur.

Status


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

Resolution


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

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:

Workaround


To work around this issue, turn off indirect checkpoints on the tempdb database by using one of the following Data Definition Language (DDL) statements.

This should be done as follows:

  • On the modeldb database (this also changes the default value for new databases), run the following statement: 
ALTER DATABASE [model] SET TARGET_RECOVERY_TIME = 0 MINUTES
  • Or, directly on the tempdb database every time that the instance starts up by using the SQL Server Agent by using the following statement: 
ALTER DATABASE [tempdb] SET TARGET_RECOVERY_TIME = 0 MINUTES
  • Or, periodically issue manual checkpoints against the tempdb database by using the following statement: 
use tempdb 
gocheckpoint 
go
In addition, TF 3468 can be used to disable indirect checkpoint on tempdb.

References


Learn about the terminology that Microsoft uses to describe software updates.