KB4016657 - FIX: Bad query plan created on secondary replicas after FULLSCAN statistics update on primary replica in SQL Server 2016 SP1

Assume that you use Microsoft SQL Server 2016 Always On Availability Groups. After statistics are updated by using the FULLSCAN option on the primary replica, the statistics on the secondary replica become stale or out-of-date. When you run a query on the secondary replica, a bad query plan might be used. This causes slow queries.

This fix is included in the following updates:

Each new build for SQL Server 2016 contains all the hotfixes and security fixes that were included in the previous build. We recommend that you install the latest build for SQL Server 2016.

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

Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×