Operational Defect Database
BugZero found this defect 910 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 14302678
KB5008184 - FIX: ForceLastGoodPlan doesn't account for aborted and timed out queries in regression detection logic - Microsoft Support
Last update date:
9/20/2022
Affected products:
SQL Server 2019 on Linux
SQL Server 2019 on Windows
SQL Server 2017 on Linux
SQL Server 2017 on Windows
Affected releases:
build lower than 15.0.4188.2
Fixed releases:
15.0.4188.2
Description:
Symptoms
In Microsoft SQL Server 2019 and 2017, the ForceLastGoodPlan feature for Automatic Tuning doesn't take CPU consumption of aborted queries into account in the execution plan regression detection logic. The feature recognizes query execution time-outs as client-side aborted queries. Therefore, it doesn't interfere. If the query that has a regressed plan is consistently timing out, the ForceLastGoodPlan feature won't detect and correct the plan regression.
Resolution
Cumulative update information This problem is fixed in the following cumulative updates for SQL Server: Cumulative Update 14 for SQL Server 2019 Cumulative Update 31 for SQL Server 2017 About cumulative updates for SQL Server Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server: Latest cumulative update for SQL Server 2019 Latest cumulative update for SQL Server 2017
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 that Microsoft uses to describe software updates.
