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:
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:
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 packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. Our recommendation is to apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article for finding more information about the latest service pack and latest cumulative update.
How to determine the version, edition and update level of SQL Server and its components
Learn about the terminologythat Microsoft uses to describe software updates.