Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


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.


Cumulative update information

This problem is fixed in the following 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:


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


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

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!