Update adds CPU timeout setting to Resource Governor workgroup REQUEST_MAX_CPU_TIME_SEC in SQL Server 2014, 2016 and 2017

Velja za: SQL Server 2017 DeveloperSQL Server 2017 EnterpriseSQL Server 2017 Enterprise Core


In Microsoft SQL Server 2014, 2016 and 2017, setting the Resource Governor workgroup configuration REQUEST_MAX_CPU_TIME_SEC doesn't prevent a request from continuing if the maximum time is exceeded.

The scope for REQUEST_MAX_CPU_TIME_SEC configuration has been changed from Microsoft SQL Server 2017. When Trace Flag (TF) 2422 is enabled, and if a request exceeds the maximum time set by REQUEST_MAX_CPU_TIME_SEC, then the request is aborted. Additionally, you may receive an error message 10961 that resembles the following:

The request has been aborted because its CPU usage exceeds the maximum configured limit for the workload group.


This update is included in the following cumulative update for SQL Server:

        Cumulative Update 3 for SQL Server 2017

Service pack information for SQL Server

This update is fixed in the following service packs for SQL Server:

       Service Pack 2 for SQL Server 2016

       Service Pack 3 for SQL Server 2014


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